Is this the correct reading? If so, I'm not that impressed.

When I stop working out, I quickly forget what calories actually cost.

- More frequent releases accelerate learning what has real value [No improvement]

- Limiting work in progress, solving one problem at a time,increases delivery throughput [Continued]

- Cross-functional teams experience fewer bottlenecks and blockers than specialised teams [Confirmed]

Empowered, self-organising teams spend less time waiting for decisions and more time getting sh*t done [Confirmed]

Additionally, smaller teams 1-3 engineers per project who are empowered are much happier. Side effect was time spent on process, tickets, communication dropped dramatically. Time spent on creating and confirming increased.

In a large organization solving your own blockers can be the difference between releasing next week and releasing next quarter. More frequent releases only help in a business where users adopt new features quickly.

My prompt,

"I'm considering buying stock in the company with symbol NU. The most important thing to me is answering the question, is the stock likely to rise in the future. Please help create a list of questions that will help me to understand the likely hood of this. Also please help to anwser those questions. Please highlight the global economic environment for the company. Any unique challenges and unique advantages. Finally let me know what others think of it"

Results: I know this stock well all though I'm not a pro. It nailed all of the relevant aspects and hits the analysis right on for everything I know about it. Pulled lot's of helpful resources and most importantly the information was timely enough to be relevant. The timely part is where other LLMS have failed miserably. I've gotten good analysis from other LLM products but they have always been way out of date which makes them useless.

Each team needs to develop a process that meets the needs of the group. For some teams standups are useless because the team is on the high end of the communication spectrum and also on the high end of the process spectrum, meaning they communicate well and update their tickets. Other teams are on the low end of both of these and benefit from standups and management structure that forces improvements to both of those.

Agile is about building systems, tools, and processes that allow your team to win. That requires understanding how your team operates and what they need to do their best work. There will never be a right answer to the majority of these types of questions.

When I was 20 I worked at Costco while going through college and one of my coworkers was previously a software engineer at sun microsystem. He ended leaving the industry because his skills were up to date enough but he was happy in life and had paid for most everything he needed already. It would be unpleasant to go through but make wise financial decisions and ride it out as long you can. Also I maximize my 8 hours a day and do my best to learn on the job.

While my current lifestyle doesn’t lineup well with the tech grind and won’t get me attention online I’m much happier living a lifestyle that serves me and family rather than some external validation. Hope that helps and good luck on your journey.