Some of my saltiness comes from the fact that I tried to answer questions a few times, but told I wasn’t worthy enough to participate in the conversation, and so I was confused by the system. Also, I saw people answering with lots of points, but their answers were trash and I couldn’t impact that response/point gathering, and just made me think it was just another gamified system, and engineers love to game a system. :)

This was my experience as well. They seemed to angle the system away from the casual user, which I didn’t have time to sit around and answer questions to get enough fake internet points to interact more.

That is 100% up to every team to decide. Version numbering is completely arbitrary.

Good read, thanks for sharing.

I’m teetering on this edge currently. “Oh, I haven’t made GitHub contributions to my two open source projects in awhile, and I need to brush up my coding skills in case I cannot find another Director level job, and …” then I’m exhausted and dreading the next day’s meeting schedule.

I’m always curious about this particular feature/argument. From the aspect of “i can unit test easier because the interface is abstracted, so I can test with no database.” Great. (though there would be a debate on time saved with tests versus live production efficiency lost on badly formed automatic SQL code)

For anything else, I have to wonder how often applications have actual back-end technologies change to that degree. “How many times in your career did you actually replace MSSQL with Oracle?” Because in 30 years of professional coding for me, it has been never. If you have that big of a change, you are probably changing the core language/version and OS being hosted on, so everything changes.