1
point
dottedmag
Joined 900 karma
Mikhail Gusarov
Another self-taught software engineer.
https://dottedmag.net/
- I don't see it challenged before the MR.
Linux caught Kent when he tried to sneak in non-bugfixes into a RC, and berated him.
After that (not before, this is a critical distinction) Kent said "I don't want to abide by the rules, because I have my concerns".
This is very similar to the situation I have described, except that in Linux it was Linus who was skipping reviews on Kent's code trusting him not to subvert the rules, and in situation I described the team collectively was trusting each other not to subvert the rules.
- I didn't make myself quite clear — the others were raising points on _other_ rules, and as a result we tuned the rules quite often, as we discovered what works better and what works worse.
Except one person.
- It is, but directly, not as a subversion.
I have had a similar experience with a team member who was quietly unhappy about a rule. Instead of raising a discussion about the rule (like the rest of the team members did) he tried to quietly ignore it in his work, usually via requesting reviews from less stringent reviewers.
As a result, after a while I started documenting every single instance of his sneaky rule-breakage, sending every instance straight to his manager, and the person was out pretty soon.
- Except that every month bits of that value get chipped off.
- PostgreSQL server is a single process that starts in under 100ms on a developer's laptop.
In the company I work for we use real PostgreSQL in unit tests — it's cheap to start one at the beginning of a suite, load the schema and go, and then shut it down and discard its file store.
I keep thinking of moving that file store to tmpfs when run on Linux, but it's nowhere near the top of the performance improvements for the test suite.
So: no more mocks or subsitute databases with their tiny inconsistencies.
- Serial port
Cray 1 was released 1975, teletypes were old tech at that time.
- Thank you, that's what I feel too.
For me switching the career, after spending more than 20 years in this as well... is very hard. I spent all my career outside of high-pay places like SV telling myself "I have all the time in the world, I don't need to grab most amount of money as soon as possible", so retiring is not an option.
So, switch to what? Any well-paid profession is going to be under pressure to be LLMized as much as possible.
- Will it? The author goes to my «do not hire / hype-eater» list for sure.
- Indeed, that's the only reasonable scenario that comes to mind.
- Have you really seen language chosen based on formatting?
- Should all companies expand to the whole globe?
There are plenty of well-off places with mild climate where using a scooter all year around is feasible.
- Syscalls are easy. Drivers will be tough.
- Make managers personally responsible.
- Exactly: this "license" thing has to be changed to buying digital content.
- Open source is a technical detail. One can see a less drastical change that will have the same effect.
1. Update the laws so that the shenanigans of the companies are finally named as they are:
- Retroactively removing a feature is stealing from the owner.
- Deleting bought digital content is also stealing from the owner.
- Spying on a user is an unlawful search.
2. Make these transgressions be investigated by the prosecutor's office, so that a citizen only needs to report it to them and not figure out how to get a class lawsuit going. This will allow security researchers to do their job.
3. Classify devices with unpatched and unpatcheable security bugs as "unfit for use" and eligible for a full unconditional refund, and extend warranties on them to, say, 15 years.
4. Obviously, make any kind of security research legal and protected from intimidation by the companies.
- One can argue there are ~8bln of these robots already roaming the Earth.
- There are rocky deserts.
70% of Sahara is rocky, not sandy, for example.
- Bangladesh is also large.
My faviourite configuration pattern for SaaS code: all the configuration for all targets, from local development setup, to unit tests, to CI throwaway deployments, to production is in a single Go package. The current environment is selected by a single environment variable.
Need something else configured beyond your code? Write Go code to emit configs for the current environment, in "gen-config some-tool && some-tool" stanza.