Never touched it? A website? What about updating frameworks for security issues?
Never touched it? A website? What about updating frameworks for security issues?
The closest I got to this kind of job., is the closest I got to running away. I’m much happier elsewhere now.
This, to a point.
Other things help :
Or just racist.
Where I’m from judges have to be picked by a list prepared by the bar of that jurisdiction, IIRC. That way you can’t just get any barely competent idiot who happens to be a good party man as a justice on the highest court of the land.
If a TODO passes code review, more than one person fucked up.
THIS.
All the rest of this conversation is pedantic nonsense (on both sides, I might add).
It’s like if the law decided that only fire brick red as defined by this website is red : https://html-color.codes/red
And then someone on lemmy said “the court said your car isn’t red”. And then we’d have to spend a half hour and an incredibly long post to explain how courts sometimes use different definitions for words that people use in normal conversation, and to be careful how you interpret that.
Bottom line is Trump did what everyone else is calling rape.
Takes time to become ubiquitous.
Learning to deal with “unmaintanable” codebases is a pretty good skill. It taught me good documentation and refactoring manners. It’s only a problem for you if management does not accept that their velocity has gone down as a result of tech debt pilling up.
Code should scream it’s intent (business-wise) so as to be self-documenting as much as possible As much as possible is not 100%, so add comments when needed. Comments should be assumed to be relevant when written, at best. Git comment should be linked to your work ticket so that we can figure out why the hell you would do that, when looking at the code file itself. I swear some people seem to think we only read them in PRs (we don’t). Overall concepts used everyday, if they need to be reexplained, should probably be written down (at least today’s version). Tests are documentation. Often the only up to date one?
Git wasn’t used all that much in the 2000s. As far as I know it became popular in the 2010s (though it was always a thing in some circles I think) and then just supplanted almost everything else.
Also keep in mind some shops tend to follow larger tech companies (microsoft, etc.) and their product offering. So even new products might not have been on git until MS went in that direction.
Professionals should care about their client’s privacy though. That shouldn’t be a debate.
Except that instead of an authoritarian government using it to totally control the learned populace, they are showing you ads.
We’ve still got a way to go before 1984. If it did happen, you wouldn’t be able to discuss it.
“we need more resources” is bounded by the rate at which you can incorporate new teams members without absolutely destroying your productivity, or having a bunch of untrained fools running around breaking things (of course the later is standard at many places already, so I guess it doesn’t always matter).
The right answer is usually : “No”. Or at least “Prioritize”. Or “This is what we need to get it done” at which point they might start to get software takes time to make decently, and they don’t want software that doesn’t work decently in the first place.