Any professional would have a code repository and probably a build server which spits out binaries left and right, off site of course.
Bonus points if that is the easiest way to deploy the software, so all developers actually use it.
Edit: typo
Any professional would have a code repository and probably a build server which spits out binaries left and right, off site of course.
Bonus points if that is the easiest way to deploy the software, so all developers actually use it.
Edit: typo
Insomnia suddenly turned into a ransomware. Pay up or have all you dara lost!
A few days later Insomnium popped up supporting the old file format.
“It depends” is a good answer, and is in line with me questioning the above comment.
Here’s a link to a recent huge worldwide study: https://survey.stackoverflow.co/2024/work#salary
I prefer to use statisics rather than anecdotal evidence. The stack overflow survey shows full stack pretty far down:
Why would you think full stack developers make more money in general?
“A”.reverse() === “A”
It’s even worse when you can tell they really tried and still end up with spaghetti. Even mid- to senior developers do this. Rhe more senior they claim to be are, the more embarrasing when you have to get the stick.
Some people try to be so clever with fancy design patterns or bit-tricks, instead of just solving the problem, you now have two problems and a solution to one of them.
I totally agree with you. I’m not sure that strategy works though. All they will (still) see is 0% linux/firefox users no matter if we spoof or not. It will just be fewer users.
It’s actually the company’s problem. They usually opt to add more debt though, rather that wade through the old stuff.
In the end, all software sucks and should be replaced as soon as possible. Code quality is a lie we tell ourselves so that we can sometimes be proud of our work. It’s usually the code we are most proud of that is the worst. Design patterns everywhere making the vode overly convoluted and “future proof”. The only future proofing that happens is that no-one will understand it, so they won’t change it. Trying to design for the future usually makes it harder in the future.
This will lead to change fatigue. People will rather not cleanup as they go anymore and just get the work done, with worse and worse code quality as a result.
Bank holidays would be really awkward. You start wort at 23 and the next day is off so you would just have to work that one hour.
Office workers could probably move hours around. It would get complicated for shift workers though. Paying overtime for work on holidays?
I’m not French nut usually the price of transmission is omitted, netting in a positive cost for end consumers. If it was really negative, there would be businesses just burning energy to make money.
Battery business should be good in the future though.
Fuzzy search solves this pretty good
Exactly! All applications can be shit, not just web sites.
People screw up CLI’s all the time (looking at you Google Cloud). They (used to) insist on using my installed python which automatically upgrades and breaks the CLI. Good job python. Good job Gcloud.
Yes you should. I think most comments here are about products that have millions of users where it’s actually worthwhile spending all that extra time and money to perfect things.
For most development, it isn’t worthwhile and the best approach is to wing it, then return later to iterate, if need be.
The same goes for most craftsmanship, carpentry in particular. A great carpenter knows that no-one will see the details inside the walls or what’s up on the attic. Only spend the extra time where it actually matters.
It triggers me immensely when people say “I could have made a better job than that” about construction work. Sure maybe with twice the budget and thrice the time.
That may lead to over-refactoring, leading to unmaintainable garbage code.
102 times if you count the one before the code.
And fuck your versioning system. And you dependency management. And tooling. Why are there like five different projects trying to lock down the python environment? Conda? Venv?
Even Ubuntu tries to lock down python so that it doesn’t brick the install due to dependency conflicts.