But guys, if we use agile then we don’t need requirements! We just make something and then the customers tell us if we are on the right track, we just get to iTeRaTe
Software Architect turned Engineering Manager
But guys, if we use agile then we don’t need requirements! We just make something and then the customers tell us if we are on the right track, we just get to iTeRaTe
There’s really good documentation out there and there’s bad/nonexistent documentation. So stackoverflow is going to be a more consistent experience.
Also I think it is a bit of a skill to be able to read documentation well, especially for Jr. Devs that might not have fully grasped OOP.
Hey, my meme I reposted got reposted to this instance’s programmer humor. Cool!
I stole it from someone else, so no worries OP. I honestly just like how Lemmy can enable these “reposts”. I think it’s fun that someone else that a dumb meme I thought was funny was actually funny enough to post it again.
My favorite project was C++; it was big, it was complicated, there was a massive team working on it, I got to work with high level abstractions while occasionally dealing with really low level concerns.
It was really hard, but now writing code in every other language I’ve worked in has been really easy.