287 karma · joined September 14, 2016
10 years experience as a full stack dev. Currently leading a team in the AgInsurance space. I enjoy working on problems and with tech. Looking for a position that allows me to work on interesting problems, develop but also engage asva leader. Preference for greenfield work with startups and on developer tools especially.
All that to say this: we wanted cutting edge language features, beautiful UI and didnt want the page to flash white when we did something so we stopped switching pages and handled state on the front-end. Not sure it was all worth it tbh.
The main catalyst for leaving is pay. If i could find another company that would pay me more I'd present that to my current employer and if they couldnt match it then off I go. Usually I wait a while to start looking.
I saw one comment hear talking about maintenance and consequences and that's interesting! For myself, I gravitate to greenfield work. Startups and the like. Your code doesnt always live a long life in those environments and prehaps this shields me from the worst of the maintainability issues. Ive actually grown distasteful for to much "maintenance programming efforts" as I've seen months of such work disappear after a pivot (replaced a series of sequential forms with a table view once after the team spent months getting the forms right. Sad.) I believe that 'bad code' that takes you from 0 to 1 is a good headache to have. I've also seen people call code bad when i saw no issues with it (terria.js) and went on a months long run to rewrite a frontend months from release. Went about as well as expected. Code got written to replace already working code. No comment on whether it was better or not but my opinion is a likely no. There's a level of subjectivity to code quality that i think gets lost on people sometimes.
Secondly the worst code you've ever seen is capable of pulling in 20 mil per year. Was the best? There is something to be said for success and it really makes me wonder about what 'good code' really is suppose to look like.
Granted a lot of what you're describing sounds terrifying.
If you want to deal with it first thing you should do is stand up a testing server and backup the code. Get some E2E tests in place to keep track of expected behavior. All of this can be done without removing a line of code and you can do it yourself while the team goes about their merry business. This is where I would start.
Rust seems like an interesting choice for you since it's a system language but also gets used by web devs in some situations. Go might be another good choice.
Again though, it all depends on what you want to do with your time.
Tldr if you're making code dry and you insist that you make code dry across feature boundaries then for the love of god make unit tests for those functions. Or keep your functions dry and your features wet.
stardew valley meets fallout.
Subnatica in space. Inspired by an episode of love death plus robots.
A cli todo list in 40 lines of bash https://news.ycombinator.com/item?id=31034532
Creating aliases from bash history with bash https://news.ycombinator.com/item?id=31034185
IMO redo and my script are nice enough but, day to day, I've found making aliases from the last command I ran more useful.
Hope ya'll find it useful for something!
I agree with your last paragraph and your first but that second is a doozy.