3,112 karma · joined May 4, 2021
He's shopping around. When something is out of his budget it's natural to not buy.
The absurdity of 140k weekly downloads is a result of CI/CD practices.
I'm probably in the minority here but I think npm and github should actively disallow (or atleast discourage by making it very uncomfortable) to re-download the same dependencies from the internet on every pull request.
"features": {
"copilot": false
}Email: consult@judi.systems
I am consulting as an architect for web development teams. Bridging the gap between product requirements and concrete implementation details.
If your team is having problems completing work on schedule, or you’re not satisfied with development velocity, and feel the need to hire more programmers to help finish the work on time, please reconsider.
It’s highly likely that what you need is not another programmer. Instead, what you need is someone to fill the gap between product requirements and specific implementation details.
If you could give your team a technical document describing how to implement a feature, it will help them do the work in a shorter amount of time to a higher quality standard.
This is what I hope I can deliver for you and your team.
For more details: https://judi.systems/consulting.html
I also find their layout "framework"/API to be weird and counter intuitive.
It all looks staged or planned by someone or something.
The key to find out is to look for a business move that used to be illegal but now became legal due to the unfolding events.
It's like economic transactions, which the state already tracks.
Why are you labeling it as "evil"?
This is not a matter of fact. It's an emotional projection stemming from refusing to succeed.
Martyr syndrome.
To each their own, I guess?
My hypothesis is the design of the page and the images played a big role in convincing people this is "legit".
Why would anyone replace a literal byte in memory with a full program?
Why?
It's just code.
If the team is so bad that an intern can mess things up, they will, and the mess will have nothing to do with feature flags.
Using Docker for setup a C development environment indicates that there are too many moving parts and the development environment is essentially very complex and that there's nothing that one do about it.
I wish more people would write such guides with the aim of reducing the development environment to its essentials that can be installed system-wide without being disruptive and thus not needing "Docker".
What actually hides being it is: unless everyone cares about it, then no one cares.
What if only one in a thousand people care? That's a huge number. You could have 10k or 100k readers.
It's a minuscule number compared to everyone, but it's a huge number for a blog.
100% anyone who tries this will fail
It only appears to work if you think that kind of advertising is how they got to their market position. Usually it's not.
Let's Docker for an example.
Docker did not get adoption because of some cliche marketing on their landing page. It got adoption from people doing tech talks and tech demonstrations and several companies writing blog posts about how migrating to Docker saved them from the headaches of deployment they were having before with the ad-hoc systems.
Complex enterprise tech gets sold by other means, usually personal relationships with key decision makers, and maybe some amount of bribery, who knows.
It obviously doesn't work.
Can you imagine a restaurant flyer that just says "Enjoy delicious meals! Have fun time!"
It's absurd.
You show pictures of the food. Tell people how you source your ingredients. How your chefs have perfected their craftsmanship. Etc etc.
It means the commit only needs to make sense to my self until next week.
If I see a commit from 2 weeks ago and I don't know what the message means, who cares? I hardly look at those commits.
I use commits as rollback points. If something works and I want to try something risky, I commit first. I don't care about the commit message. I basically never look at any commit older than one month
You can pretend that's not the case all you want.
He's the one who wrote BoltDB https://github.com/boltdb/bolt
I just put a relatively thin layer on top of it.
Now, to address your point more directly: I'm too stupid to figure out configuration, but not too stupid to figure out code. Code gets compiled and type checked. You can have tests, etc. Tractability for code is much higher than configuration.
With configuration, you have to be really smart and keep many moving parts in your head.
With code, you can be a bit dumb and lean heavily on the tooling.