| Privacy | Agile software development |
| Java | Typescript |
| React | Programming |
I accidentally found a security issue while benchmarking postgres changes.
If you run debian testing, unstable or some other more "bleeding edge" distribution, I strongly recommend upgrading ASAP.
I wanted to take a few moments and apologize to many of my former students.
In the past I said the industry needs people who look at security as a vocation and an avocation.
I was wrong.
Have a life outside of this industry.
Have hobbies that have nothing to do with your computer.
Get outside.
The problems of the industry are not problems of people not working hard enough.
They are not problems of people not being "hard core" enough.
They are problems of education and resource prioritization.
I was wrong.
I am sorry.
Stop breaking yourself on rocks for people who don't really care if you break yourself on rocks.
Apparently "writing code that solves the business problems" is way less exciting than creating shared libraries, minor iterations of code style, automating linting and working on pipelines.
My guess is that it's because the latter requires no specific business knowledge of concepts, and is more transferable
My second guess is that recognition from tech peers is probably worth more to them than recognition from the POs and business leaders
It makes me sad as that stuff adds little value
Exactly 14 years ago , Satoshi Nakamoto designed the most pathetic / inefficient system ever invented by humankind : the blockchain.
Today, it weights 60 000 tons, wastes constantly 10 gigawatts (more than Belgium or Chile) to process less than 7 transactions per second :
Less than a 33 bps modem from 1990.
This could be a joke if it didn't have such gigantic environmental impact, wasn't enabling billion dollars ransomware industry and was not crushing thousands of lives in the process.
One aspects of Agile software development is to work concurrently
On a typical week, my team will be observing or talking to end users, sketching design ideas, pair programming key parts of the future system, meeting with technical experts to understand technical constraints and possibilities and deploying things to our servers
The activities support and enable each others. For example, when implementing code, we may come to with questions to ask at our next meeting with users
The Problem With Dependency Injection Frameworks: A 🧵
Right before the weekend, I wrote a snarky article about my gripes with dependency injection frameworks. Here's the thread I promised about it.
Here's the article: https://www.jamesshore.com/v2/blog/2023/the-problem-with-dependency-injection-frameworks
1/
6/ Magic frameworks are bad:
They're sorta cool when they work, but absolute hell when they don't.
5/ I'll give a quick summary of the arguments for each point. Read the article for details. (https://www.jamesshore.com/v2/blog/2023/the-problem-with-dependency-injection-frameworks)
Third-party code is expensive: People's build vs. buy is wrong. You’re not comparing the cost of building and maintaining it yourself to the cost of buying it from someone else. You’re comparing it to the cost of buying it, learning it, working around not-quite-right behavior, keeping up with updates, and dealing with incompatibilities.
AndresFreundTec
Geir Storli Jensen
John Strand
MartinDotNet
Franck Leroy
Anders C. Sørby 🔥🌍 🇵🇸🇸🇩🇨🇩🇺🇦🌻⚛️
James Shore