Here on break

  • 0 Posts
  • 67 Comments
Joined 1 year ago
cake
Cake day: June 16th, 2023

help-circle




  • I know some Java folks, but my sampling is biased because I meet them where I work - places that predominantly use the younger languages. Actually, I happen to know that the MoH in particular (and probably lots of other institutions) wrap their COBOL/JCL in a lot of Java, so that most devs never need to dive into the “real backend” if they want to just stay at the Java level.

    Java people seem like family people. But from what I’ve observed, their job doesn’t seem any different. You can work in javascript, or python, and still insist on clocking out at 16, 1700. But I only work at startups or seat of your pants kinds of places, so I know about what I hear. 🤷












  • Man I don’t regret leaving this behind at my last job. You start out by doing someone a one-off like “sure I can pull the top 5 promotional GICs broken down by region for your blog article - I love supporting my co-workers!”

    Then requests become increasingly esoteric and arcane, and insistent.

    You try to build a simple FE to expose the data for them, but you can’t get the time approved so you either have to do it with OT or good ol’ time theft, and even then there’s no replacement for just writing SQL, so you’ll always be their silver bullet.



  • Peer reviews can catch bugs that tests can’t catch.

    I won’t disagree that peer reviews are overrated, but they’re a great way to train and onboard less experienced devs (who are just more fun to work with, anyway). Like I’m a platform dev, so I don’t have a “home” project - if I had to know every project before I opened a PR for it, I’d get hardly any work done. Review help other knowledge experts weigh in on my changes.

    Anyway, one case for being pro