this post was submitted on 13 Apr 2024
409 points (100.0% liked)
Technology
37747 readers
181 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
He's got a point, though, the further you go, the less time you spend inputting code. Although some people prefer to continue going head first and then remaking everything.
That is a lot of fun to do, most times. Also I need to provide for my family and the guys who pay my salary want their stupid features implemented like yesterday.
I half agree about fun, think it depends on how often clients want some weird shit done yesterday, it becomes a nightmare if it happens too often :(
like with many jobs you're learning to only do the work that matters, and oftentimes when you can avoid doing work that actually improves the product.
There's a reason why construction workers aren't making their own planks and nails, that would be horribly time consuming, inefficient, and they'd probably make shitty planks.
Not trying to become an expert in everything was the most important decision I made so far, I think
Over the past month I feel like all I've been doing is writing tech design documents for systems I don't actually know anything about because I haven't had the opportunity to go in and do anything with them.
Fortunately I've finally managed to reach the point where everyone agrees that we should just start implementing the basics and see how that goes rather than try to plan it all out ahead of time since we're surely going to have to throw out the later plans once we see what we're actually dealing with.
Absolutely. I barely touch code anymore, but I talk about how to touch code a lot.