Though, a PR that introduces dead code (function that isn't called anywhere) wouldn't get approved by me :)
1,876 karma · joined July 31, 2013
Though, a PR that introduces dead code (function that isn't called anywhere) wouldn't get approved by me :)
As as senior engineer, either I want to review every single change that's being made and I should be doing pair programming anyway, and PR approval is almost purely symbolic.
Or, I trust my colleague enough that I'll spend 5 minutes looking at their justification, explanation, testing strategy, rollout plan and decide to trust their code.
Stacked PRs and insisting on small PRs seems to want to fill some gap in the middle between these two, which isn't necessarily the correct solution.
{{ "--quiet" if ansible_verbosity == 0 }}
https://jinja.palletsprojects.com/en/3.1.x/templates/#if-exp...> some poor soul comes along and asks a question that's 5 years out of date because they found it on the wiki
This happens if there's docs in a git repo as well.
How do you deal with cross-cutting concerns, docs that span multiple code repositories?
I think the key insight is, it's not worth focusing too much on this segment, except in very specific markets (maybe super-expensive sofware, like the Adobe suite, DAWs, AutoCAD etc.). The majority of paying clients don't go through this amount of effort, and unless they're cheapskates (in which case you might not want them as clients regardless), will just pay and be honest customers, appreciating regular updates and support.
oh not to mention the statefulnes of it, it was almost impossible to destroy and re create an instance from scratch without a bunch of manual point and click via the UI.
Sometimes I ponder about business opportunities catering to the upper end market, making things ridiculously expensive just to capture the super rich segment, and using the profits for good in society (somehow).
Most people/businesses don't operate like this I suppose - they just want a yacht of their own, or to infinitely grow their business.
I also think your description is very iffy. "A market which approaches a state of perfect competition" depends on what amount of competition you think is perfect. Furthermore, it could be achieved either through regulating or not regulating (depending on what you think "perfect" is), so the term doesn't really say anything about actual policies.
The very intuitive meaning of free market is an unregulated one, IMO. I'm not able to find an ubiquitous or official definition, but most top google results lean in this direction.
I do think that conflating the means (unregulated market) with the end goal (perfect competition market) into the term "free market" is a brilliant marketing move for free market advocates, but it's somewhat dishonest.
Similarly, while I could pay 2-3 times more for a Fairphone or such, it'd be better if tech independence was available to everyone, including for consumer-grade smartphones.
On a related note, I think devices such as Fairphone and Framework laptops prove that even without regulation, "free" (as in freedom) products are already more expensive, you don't need regulations to make that happen.
Looks cool though, and has a nice backstory.
Metal concerts are loud sure, but the loudest concerts I've gone to have been electronic or indie stuff with heavy electronic influences - they try to make you feel like you're in a night club I guess.