3 ms·
Realistically any code base where the engineers had at least a basic understanding of programming. You do not know suffering until you've seen someone hard code
by 999900000999 2y ago
Realistically any code base where the engineers had at least a basic understanding of programming. You do not know suffering until you've seen someone hard code basic variables, we're talking about strings all over the place, and then they just copy the function again to replace the strings .
I've legitimately left jobs over bad code. We're talking about code that did nothing in reality.
The best code bases have been ones where I've been able to lead the direction. I get to know exactly how things work. I'm privileged to have a job where I essentially created the initial framework right now .
Plus I'm fully remote, life is pretty good.
- naikrovek 2y ago> any code base where the engineers had at least a basic understanding of programming I felt this in my soul as soon as I read it. The number of people writing code who should not even be speaking to others because of how clearly they don't understand anything technical is unfathomably high. Our industry hires seat fillers and tells them to write software. And then they do, and it's every bit as bad as it sounds.
- withinboredom 2y agoSame. Some genius hired a "software architect" who doesn't know how to write code. When I asked the genius why he would do that, he said it was because regular architects don't know how to build houses, so why would he know how to program? That was some next-level shit. He showed us a diagram once where the database was calling github which was calling a microservice. These are the days before Github had a CI, so it was pretty funny.