Kind of the opposite actually.
The Business™️ used to make all decisions about what to build and how to build it, shove those requirements down and hope for the best.
Then the industry moved towards Agile development where you put part of the product out and get feedback on it before you build the next part.
There’s a fine art to deciding which bugs to fix win. Most companies I’ve worked with aren’t very good at it to begin with. It’s a special skill to learn and practice
That’s why I don’t work on mission critical stuff.
If my apps fail, some Business Person doesn’t get to move some bits around.
A friend of mine worked in software at NASA. If her apps failed, some astronaut was careening through space 😬
You might check to see if Eater has a site for your city/area
🐬 Improvised Underwater Timekeeping for Dolphins:
An intelligent dolphin could adapt to underwater timekeeping by observing natural cycles, biological cues, and marine phenomena. Here’s how:
Harnessing Natural Rhythms
• Tidal Changes: Dolphins could monitor the ebb and flow of tides, which occur predictably based on the lunar cycle. Changes in water current speed, temperature, or pressure could serve as cues for time measurement. • Day-Night Cycles: Despite being underwater, ambient light penetration varies with time of day. Dolphins with sensitive vision could detect shifts in light intensity or color. • Marine Sounds: The ocean environment is rich with natural sounds that vary throughout the day, such as coral reef activity during daylight hours or nocturnal hunting sounds.
Biological Cues
• Internal Circadian Rhythms: Dolphins have well-developed biological clocks that could help them estimate time intervals based on their innate circadian rhythms. • Heartbeat or Breathing Patterns: They could track their heart rate or breathing intervals to measure short durations.
Environmental Markers
• Bubble Streams: Dolphins could use their breath to create bubble trails or patterns and observe their rise time or behavior as a rough timing mechanism. • Floating Particles: They could monitor the sinking or rising of particles like algae or debris to estimate time.
Intelligence and Communication
• Echo-Location as a Timer: Dolphins use echolocation effectively. They might develop a way to measure time based on how long sound waves take to bounce back from consistent underwater structures. • Social Synchronization: In groups, they could rely on collective signals, such as patterned clicks or whistles, to denote the passage of specific intervals.
Innovative Tools
• Natural Hourglasses: They could manipulate objects like sediment-filled shells, observing how long it takes particles to settle or rise when shaken. • Thermal Layers: Dolphins could detect thermal gradients or changes in water temperature at specific times of day.
It’s usually the implementation of Agile that’s bad.
The Manifesto’s organizing principles are quite succinct and don’t include a lot of the things that teams dislike.
We follow these principles: Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Business people and developers must work together daily throughout the project. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. Working software is the primary measure of progress. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. Continuous attention to technical excellence and good design enhances agility. Simplicity--the art of maximizing the amount of work not done--is essential. The best architectures, requirements, and designs emerge from self-organizing teams. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.