• 0 Posts
  • 17 Comments
Joined 3 months ago
cake
Cake day: March 31st, 2025

help-circle
  • For me it’s less about fear and more about having a limited budget of time and effort to spend on learning things, so CSS and front end generally gets deprioritized. But that’s cuz I’m a back end kinda dev in my soul, lol.

    I’ve seen the good points you’ve made elsewhere in this thread - I would indeed react very poorly to willy-nilly back end changes and I think you’re right that people don’t give CSS and visual styling the same degree of professional respect when making changes. And that sucks.





  • I enjoy and appreciate nature in nearly all its forms. Even mosquitos just tryna live, they’re born required to bite somebody 🤷‍♂️

    Fuck the Canada goose.

    Fuck em as a group, fuck their whole flocks, fuck a flying V of Canada geese. Fuck em as an entire grand, branching lineage of this strange fractal miracle we call life, get rid of the Canada goose and our timeline returns to the more harmonious path it had been on before everything stopped making sense.

    Canada is cool, fuck that goose tho.




  • That’s a useful way to look at it, as verbose / extended documentation (amounts to exhaustive usage examples, if you’ve got thorough tests).

    I don’t have a metric that’s quick to relate, but for me the…attractiveness or value in testing relates heavily to:

    • Project lifecycle - longer and slower -> more tests
    • Team size (really more like 1st derivative of team size…team “churn”?) - larger, changing faster -> more tests

    Both of these are influenced by your description of tests as docs. Onboarding new engineers is way, way easier with thorough tests, for the reasons you’ve mentioned. Plus it reduces that “gun shy” factor about making changes in a new codebase.

    But it’s not always better. I’ve been writing less (few, honestly) the last year or so, sadly.






  • I would love that! I do think there are probably interesting underlying personality factors / preferences for a lot of this stuff as well.

    I do think that many of Python’s characteristics map to my own personality and I bet there’s something to that. Things like syntax of course, but not strictly syntax, also things like “The Zen of Python”, and the way its a “jack-of-all-trades, master-of-none”. I also really kind of need the freedom and accompanying responsibility to break any “rules” on a whim (Python will happily let you overwrite its own internals while running, for instance), but I almost never do anything that uses it…

    I could probably keep going lol. Feels like a “people looking like their pets” scenario, lmao



  • Sounds much like PowerBI, which I can’t say I’ve used much directly. But every time we use it, because the client likes the idea and it can theoretically do “all the business intelligence” natively…we eventually find it can only do 80% of what they actually want, which completely removes its single advantage and forces us to go custom anyway. We’ve stopped offering it, to be clear.


  • Couldn’t agree more. Field service is one hell of a drug. Money’s good, variety is fun, the chaos and travel are fun too, and you learn a lot quickly. The latter often because some or all of the mfg. plant you’re visiting needs you to fix your stuff so they can run, and no one is coming to BFE to help you, lol.

    But that all wears off, in time, and it starts to take a huge toll like you described. Never met a long term field service engineer with a healthy home life, or with their health in general. I got out because both of mine were crumbling, for real.