809 karma · joined September 28, 2011
https://github.com/DonDebonair
"It is difficult to get a man to understand something, when his salary depends on his not understanding it." -Upton Sinclair
The way to build trust and create autonomy while also keeping surprises to a minimum, is to tell your team what you expect of them and why. And crucially, you ask your team about their plan on how to get there. This still lets them decide on the “how”, while you can step in if you feel the plan is wrong. That is verification and it helps.
I think there is not a lot of overlap between people who need to automate infrastructure and people who don't know how to install Python on their development machine.
As for your other comments regarding Python as a language: I mostly agree. I have stepped away from Python as a language to develop production software. In Python I miss the confidence I get from static typing. Having said that, for automating infrastructure, you're effectively comparing Pyinfra and Python to bash scripts and YAML (for things like Ansible), which are both orders of magnitude worse if you like static typing or any form of being able to verify what you wrote.
OTP has either a usability issue or a marketing issue
One thing I find disappointing though, is that this framework is built on top of FastAPI. I feel it’s a bad idea to build on top of what’s basically a one-man project. No matter how popular that project is.
I think it confuses causation and correlation by claiming that having more people, faster population growth, leads to finding solutions to major problems humanity deals with faster. I don’t buy that. In fact, I’d say our inventiveness has been the _cause_ of both population decline and solving the major issues the article mentions (like progressing agriculture to use less resources)
I also think it takes a too anthropocentric stance. In the beginning of the article it claims that population decline is bad for the planet, but surely humanity going extinct does not have a net negative effect on the planet. As many climate change critics are prone to point out, nature will do what it wants despite the influence of humans and nature will adapt with or without us.
On top of that, triggers are hard to test.
I think people mistake “manager” as being people without tech skills. I think a tech company should have managers to create alignment and those managers should spend part of their time “managing” and part of their time still honing their tech skills.
Nobody is suggesting that Coq should be used, so stop bringing it up (strawman). And yes, Coq might have an even stricter and more expressive type system than Rust. But nobody is asking for a perfect type system (no true Scotsman). People are asking to be able to prevent users of your library to provide illegal values. Rust (and Haskell and Scala and Typescript and ….) lets you do this just fine whereas Golang doesn’t.
And personally I would much rather have the compiler or IDE tell me I’m doing something wrong than having to read the docs in detail to understand all the footguns.
My personal opinion is that - even though I’m very productive with Golang and I enjoy using it - Golang has a piss poor type system, even with the addition of Generics.
Yes, more competent hires do a better job. But there is a limit to how much competence you can hire per person. That means there is a limit - or at least severe diminishing returns - to how much more competence money will buy you.
That means you can opt to spend that money on DEI without losing out on competence
The comparison is simple: given that you want to hire a fixed number of people and you don’t want to lower the bar (hire based on merit), you can either not invest in DEI or spend extra time/money on getting diverse hires without lowering the bar.
- Take more time finding suitable candidates
- Invest money in external recruiters
- Lower the bar
Only in the last case does it come at the cost of merit
Furthermore, the evidence comes from a guy on Twitter who is primarily concerned with raging against “Leftists”.
I think we can safely ignore this evidence
There should preferably be one open protocol for proximity based wireless ad-hoc file sharing. This protocol can then be implemented by operating systems and/or userland implementations
Traditional RDBMSes just don’t scale so well as S3. But S3 didn’t have ACID semantics. Now it does!
As to why it is so popular: despite its faults, it offers a very slick experience for note taking, building a knowledge-base/wiki and project management and anything in-between really. I find the way you can store data in a structured way using Notion databases and present it in different forms very useful.