They are both deployment strategies and architecture.
1. Deployment schema is part of architecture.
2. At a coarse enough level, you don’t need to know about the structure of the system.
Architecture does not take place at one level of abstraction and it is not just UML diagrams.
𝗔𝗹𝗹 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗘𝘀𝘁𝗶𝗺𝗮𝘁𝗶𝗼𝗻𝘀 𝗔𝗿𝗲 𝗪𝗿𝗼𝗻𝗴, 𝗕𝘂𝘁 𝗡𝗼𝗻𝗲 𝗔𝗿𝗲 𝗨𝘀𝗲𝗳𝘂𝗹
If you're working in a team using the Scrum framework, you use story points to estimate effort on your stories, tasks, etc. Yet, you're probably often mistaken with estimations.
The main reason for this is that estimations are 𝗮 𝗳𝗼𝗿𝗲𝗰𝗮𝘀𝘁, and a forecast predicts an unknown future. Yet we all know it is impossible to see the end, but they tend to forget it and make commitments based on estimations.
In general, it is 𝗴𝗼𝗼𝗱 𝘁𝗼 𝗵𝗮𝘃𝗲 𝗽𝗹𝗮𝗻𝘀 because it's how we can iteratively work on something, continuously providing value to our clients. Yet, projects are usually very complex, involving many teams and dependencies between them.
𝗪𝗵𝘆 𝗱𝗼 𝗽𝗹𝗮𝗻𝘀 𝗳𝗮𝗶𝗹? There are several reasons for this, including unclear requirements and the level of knowledge not being adequately considered.
Yet, there are some other things 𝘄𝗵𝘆 𝗲𝘀𝘁𝗶𝗺𝗮𝘁𝗶𝗼𝗻𝘀 𝗳𝗮𝗶𝗹:
𝟭. 𝗛𝗼𝗳𝘀𝘁𝗮𝗱𝘁𝗲𝗿’𝘀 𝗟𝗮𝘄: States that, "It always takes longer than you expect, even when you take into account Hofstadter's Law." It highlights the recursive nature of estimation, where considering the complexity of a task and human optimism often leads to underestimation.
𝟮. 𝗕𝗿𝗼𝗼𝗸'𝘀 𝗟𝗮𝘄: "Adding manpower to a late software project makes it later." This law highlights the negative consequences of increasing team size to expedite a project. New team members require time to get up to speed, and increased overhead communication further delays the project.
𝟯. 𝗣𝗹𝗮𝗻𝗻𝗶𝗻𝗴 𝗙𝗮𝗹𝗹𝗮𝗰𝘆: This cognitive bias causes people to underestimate the time and resources required to complete a task. In software estimation, developers may need to pay more attention to potential obstacles or be optimistic about their abilities, leading to inaccurate estimates.
𝟰. 𝗕𝗶𝗸𝗲𝘀𝗵𝗲𝗱𝗱𝗶𝗻𝗴: This law states that people tend to focus on trivial details rather than critical aspects of a project. In software estimation, this can result in an overemphasis on understandable tasks while underestimating more complex tasks.
𝟱. 𝗣𝗮𝗿𝗸𝗶𝗻𝘀𝗼𝗻'𝘀 𝗟𝗮𝘄: "Work expands to fill the time available for its completion." This law suggests that if a deadline is too generous, developers may spend more time on a task than necessary, leading to inefficiencies and delays.
So, what can you do about it? Break down tasks by 𝗱𝗲𝗰𝗼𝗺𝗽𝗼𝘀𝗶𝗻𝗴 𝗹𝗮𝗿𝗴𝗲 𝗰𝗼𝗺𝗽𝗹𝗲𝘅 𝘁𝗮𝘀𝗸𝘀 into smaller, more manageable ones. For example, we found that jobs estimated up to 3 days of work are accurate.
@tamaybes Is it weird that when it does this to me I understand it? 😳
I’m like “dude, that’s how I talk about processes and nobody gets it - how did you pick up on that?” But then I just prompt it some more.
You think you are your thinking. This is not what you are. The brain exists within a sensory system that emits chemical and electric signals. Most information processing occurs outside of thought giving rise to thought rather than the inverse. LLMs have been designed from the outside in, the brain evolved from the inside out.
We are good at making machines approximate what we do, LLMs are designed to mimic thought and information processing. Consciousness was not in the design brief, emergent behaviour does not imply consciousness it implies side effect. There is no need for the machine to be conscious, it performs no relevant task that produces the desired behaviour of the machine we are created, thus there is no driver for its generation.
Why can’t “consciousness emerge from silicon”? Because it wasn’t in the specs.
Do you seriously believe aliens created something that fires 50,000 laser pulses per second at 25-micron tiny droplets, creating plasma around 220,000 K (~40x hotter than the Sun’s surface) to print features on the order of 2-3 nanometers?
Alien-aliens gave it to them to speed up technological progress.
Architecture first. Identify the distributed elements. Build them in isolation with unit tests. Build integration tests around the components as you go. Build the end to end tests as you integrate the whole.
LLMs fail at holistic tasks, they cannot infer intent, context overflows.
Even if consciousness is mechanistic it’s
Probably something to do with phonon resonance across distributes parametric compounds cause we can’t track it down to simple electronic structure in the brain. LLMs just don’t have that.
I don’t believe this but an easy mechanistic evolutionary argument would be:
Constraints imposed on the system due to fear, aggression, mating, hunger, etc chemical responses required a higher level abstraction to enable performance in hierarchical social structures to improve group survivability due to lower level impulses leading to unresolvable conflict and death, the ability to reason about future concerns over immediate desire protects the individual and members of the group.
Humans are so good at making tools that, when tasked with making a tool to trick humans that it is sentient, we made a tool that tricked the people who made it into thinking it was sentient.