Ask HN: My company is forcing 1 week sprints. What should I do?
(ycombinator.com)
The leadership of the company I’m at is forcing all teams to do 1 week sprints instead of 2 because they believe that they can get more out of the teams and get better visibility into progress.
The leadership of the company I’m at is forcing all teams to do 1 week sprints instead of 2 because they believe that they can get more out of the teams and get better visibility into progress.
Rigor and Urgency
(blueberrypediatrics.blog)
Blueberry is a 24/7 clinic startup. We need to move fast and not break things. This requires us to have a disciplined balance of rigor and urgency.
Blueberry is a 24/7 clinic startup. We need to move fast and not break things. This requires us to have a disciplined balance of rigor and urgency.
Why I'm No Longer Talking to Architects About Microservices
(container-solutions.com)
It happened again last week. I was at an architecture review meeting when a fellow architect eagerly started another debate about *microservices*. Within minutes, eyes glazed over and we were knee-deep in an absurd discussion about something that should have been a means to an end, but had morphed into the end itself. At that moment, I realized: I’m done. I’ve finally sworn off talking to architects about microservices. Why? Because these conversations usually go nowhere productive.
It happened again last week. I was at an architecture review meeting when a fellow architect eagerly started another debate about *microservices*. Within minutes, eyes glazed over and we were knee-deep in an absurd discussion about something that should have been a means to an end, but had morphed into the end itself. At that moment, I realized: I’m done. I’ve finally sworn off talking to architects about microservices. Why? Because these conversations usually go nowhere productive.
Isn't "trunk based development" just a complete crock of shit?
(bucket.co)
Isn’t "trunk based development" just a complete crock of shit?
Isn’t "trunk based development" just a complete crock of shit?
The reverse YAGNI
(medium.com)
This blog post focusses on the critical technology decisions (specifically on tools) that I believe are missed by techies on non-trivial software projects. At least I have missed them in the past because they seemed like “over-engineering”, and the bricks of YAGNI would be hurled around.
This blog post focusses on the critical technology decisions (specifically on tools) that I believe are missed by techies on non-trivial software projects. At least I have missed them in the past because they seemed like “over-engineering”, and the bricks of YAGNI would be hurled around.
Principles for product velocity
(ssoready.com)
Building the right thing shouldn't take very long -- doing away with nonsense makes product development really fast
Building the right thing shouldn't take very long -- doing away with nonsense makes product development really fast
Against the 'QA‐Free' Philosophy
(github.com/getlago)
I recently watched Pieter Levels' interview with Lex Friedman and dove through the comments. Most discussed one hallmark topic: Pieter’s 1-click deployment system that only leverages local tests for testing. In Pieter’s own words, he’s notorious for not setting up staging servers. He prefers a stripped-down pipeline, something that enables him to ship fast.
I recently watched Pieter Levels' interview with Lex Friedman and dove through the comments. Most discussed one hallmark topic: Pieter’s 1-click deployment system that only leverages local tests for testing. In Pieter’s own words, he’s notorious for not setting up staging servers. He prefers a stripped-down pipeline, something that enables him to ship fast.