Valid point but the mission is to help people appreciate each other's culture with small questions.
Eg: Question #2 was very insightful to learn about Portugal and Brazil
22 karma · joined October 29, 2018
It seems like modern Agile has mutated into a tool for Manufacturing Predictability rather than Software Discovery. We are so obsessed with making the velocity graph look like a straight line that we stopped asking if we are even building the right thing.
Do you think that shift happened because non-technical management needed a metric they could understand (tickets closed), or did we do this to ourselves?
It reminds me of Kingman's Formula in queueing theory: As server utilization approaches 100%, the wait time approaches infinity.
We intuitively understand this for servers (you never run a CPU at 99% if you want responsiveness), yet for some reason, we decided that a human brain—which is infinitely more complex—should run at 99% capacity and still be expected to handle urgent interruptions without crashing.
They didn't estimate in 'Story Points'. They used atomic physical constraints.
He described it like this:
There was a standardized metric for all manual operations like "reach, one hand, 18-24 inches" or "pick item 10-100g." Each step had a time in decimal seconds... The objective was to minimize the greatest difference in station time so that no line worker is waiting.
The most interesting part was his conclusion on the result: Modern supply management is a miracle, but manual labor today is much harsher... The goal back then was flow; the goal now is 100% utilization.
It feels like in software, we are moving toward that "100% utilization" model (ticket after ticket) and losing the slack that made the line work.
My personal favorite distinction is between the Recursive Backtracker (which creates long, winding corridors with few dead ends which is great for tower defense games) vs. Prim's Algorithm (which creates lots of short cul-de-sacs which is better for roguelikes). The bias of the algorithm dictates the feel of the game more than the graphics do.
Writing by hand (or whiteboarding) forces you to load the entire context into your working memory. AI allows you to be lazy with your working memory. The code gets written faster, but the mental model of the system in my head is significantly weaker.
If you use a Local Account (which requires bypassing the OOBE internet check during setup) or explicitly disable key backup, the key never leaves the TPM. The issue isn't the encryption algorithm its the convenience selection.
You are assuming that the founder seeking to connect is less experienced and more desperate than the founder who is busy working on their idea and does not find the need to share anything.
Google shared the Attention paper with the world. What did OpenAI bring to the table? Tesla open sourced all their EV patents. What did BYD, KIA or Ford bring to the table?
These companies are stronger because they compete on their confidence to execute and because they make the entire ecosystem better.
In doing so they improved each other and the industry as whole. Hope this makes sense. It's not a zero sum game! :)
Perhaps there are strong parallels with the application of AI for microservices architectures.
The learning can be shared between both systems. Any thoughts?
Perhaps I should have clarified I meant bouncing off ideas about execution and coffee chat on sharing inspiration on how they landed them against all odds.
People are busy struggling with their own execution challenges including myself. My point is they may not have to struggle alone by 1)learning from each other and 2)paying it forward.
Demand for new "car" is a noise. Austin FSD launch is the key differentiator and I foresee lot of sleeping on the floor moment from Elon to see it through. But if they do, the 100 year old concept of a "car" will be completely redefined.
Tesla cars are the MVPs being compared to existing automotives just like the Model T was the MVP being compared to horse carriages.
That said Elon could do an even better job of inspiring his employees on the vision if the premise of this post is indeed true.
The one's building amazing things are far and few in between due to lack of mentors in the community and hyper focus on "what's in it for me" mindset.
All the framework abstractions we made for humans coding productivity will need to be re-visited! I support plain vanilla web for this reason.