Sprints - The Biggest Mistake Of Software Engineering

ThePrimeTime
30 Mar 202426:26

Summary

TLDRThe video script discusses the misconceptions around agile software development, emphasizing that agility is not about speed but about delivering value and adapting to change. It humorously critiques various aspects of agile methodologies like Scrum and Kanban, and introduces the concept of 'Extreme Goorse,' a play on 'Garage', suggesting it as a more realistic approach to software development that values practicality and direct problem-solving over strict adherence to formal processes.

Takeaways

  • πŸ€” Agile is not about speed but delivering value sooner and being able to adapt to change quickly.
  • πŸƒβ€β™‚οΈ The term 'Sprint' in Agile might be misleading as software development is more of a marathon than a sprint.
  • 🀯 Burnout in software development is often due to meaningless tasks and a lack of progress, not necessarily the pace of work.
  • πŸ‘₯ Effective teamwork relies on individual accountability and the collective desire for change and improvement.
  • 🚫 Agile methodologies like Scrum and Kanban can sometimes lead to misery if not implemented correctly.
  • πŸ’‘ The idea of 'Extreme Goorse' is introduced as a humorous and exaggerated response to Agile practices.
  • πŸ”₯ Extreme Goorse promotes a reactive approach, only addressing issues when they surface.
  • 🌐 The manifesto for Extreme Goorse satirizes Agile principles, highlighting the importance of speed and problem-solving over strict adherence to process.
  • πŸ› οΈ In Extreme Goorse, there is no refactoring, only rework, and if a problem arises, a quick solution is applied.
  • πŸ“‹ Comments and documentation are seen as unnecessary in Extreme Goorse, as the code itself is considered the only required documentation.
  • πŸ”’ Security is considered secondary in Extreme Goorse, with trust in luck and a lack of hacker interest as reasons for its lower priority.

Q & A

  • What is the main misconception about agile software development?

    -The main misconception is that agile is about being faster. In reality, agile is about delivering value sooner and in a constant manner, with the ability to react and change course earlier.

  • What does the speaker suggest as an alternative to traditional stand-up meetings?

    -The speaker suggests using a Slack chat or a team channel where members can quickly communicate any roadblocks or issues they are facing, instead of having a formal meeting.

  • What does the term 'extreme goorse' refer to in the context of the script?

    -In the script, 'extreme goorse' is a humorous term used to describe an extreme, chaotic approach to software development, which is not actually a real methodology.

  • What is the speaker's view on the relationship between agile methodologies and burnout?

    -The speaker believes that burnout is not caused by moving fast or the expectation of moving fast. Instead, it is more likely due to doing meaningless tasks and feeling like just a cog in a machine.

  • How does the speaker describe the ideal team dynamic in software development?

    -The speaker prefers a team dynamic where members set goals together, work independently, and then reconvene to discuss progress, roadblocks, and hold each other accountable.

  • What does the speaker suggest is the fundamental problem with agile?

    -The speaker suggests that the fundamental problem with agile is its broad definition, which can lead to misinterpretations and the implementation of rigid structures that may not suit every team or project.

  • What is the speaker's opinion on the use of 'go horse' as a programming approach?

    -The speaker humorously acknowledges 'go horse' as a term from the script, but does not endorse it as a real programming approach. The speaker emphasizes the importance of effective communication, accountability, and adaptability over any specific methodology.

  • How does the speaker feel about the practice of rewriting entire applications?

    -The speaker is skeptical about the practice of rewriting entire applications, stating that it rarely works and often leads to more problems than it solves.

  • What advice does the speaker give regarding code quality and comments?

    -The speaker advises that code quality should not be compromised for speed, and that comments and additional documentation are often unnecessary if the code is clear and well-written.

  • What is the speaker's stance on the role of testing in software development?

    -The speaker believes that testing is important and should not be seen as a waste of time. However, they humorously suggest that in the context of 'extreme goorse', if the code compiles, it might be considered enough.

  • How does the speaker view the concept of refactoring in software development?

    -The speaker supports refactoring when necessary but humorously notes that in the 'extreme goorse' philosophy, there is no refactoring, only rework if something breaks.

Outlines

00:00

πŸš€ Misunderstandings about Agile and the Sprint Mindset

The paragraph discusses common misconceptions about agile software development, emphasizing that agility is not about speed but about delivering value quickly and consistently. It critiques the use of the term 'Sprint,' suggesting it implies a focus on speed rather than communication and problem-solving. The speaker proposes a more effective approach would be to address issues directly and promptly, rather than in lengthy meetings, highlighting the importance of team communication and adaptability over rigid processes.

05:02

πŸ˜“ The Realities of Burnout in Software Development

This section delves into the issue of burnout in the software development industry, challenging the notion that fast-paced agile practices are the primary cause. Instead, it argues that meaningless tasks and a lack of genuine progress contribute more significantly to burnout. The speaker suggests that the repetitive nature of certain development tasks, coupled with a lack of accountability and engagement, can lead to dissatisfaction and attrition. The paragraph also touches on the limitations of methodologies like Scrum and Kanban, and the speaker's preference for a more flexible and goal-oriented approach.

10:03

πŸ’‘ Agile Manifesto and the Extreme Goorse

The speaker humorously introduces the concept of 'Extreme Goorse,' a play on the Agile Manifesto, which is described as a Brazilian interpretation of agile methodology. The paragraph satirizes various aspects of software development, such as the focus on speed over quality and the reactive nature of problem-solving. It also pokes fun at the idea of constantly rewriting code and the lack of respect for standards, suggesting that in the pursuit of speed, developers may sacrifice important principles of good coding practice.

15:04

πŸ› οΈ The Challenges of Team Building and Project Management

This paragraph addresses the practical challenges of team building and project management in software development. The speaker argues against the idea that teams cannot be changed or replaced once established, suggesting that a competitive wage can attract skilled developers. The paragraph also emphasizes the importance of delivering software consistently and the unrealistic expectations set by new frameworks that focus on speed rather than sustainable development practices. The speaker advocates for a more measured approach to development, one that values long-term success over quick wins.

20:04

🎯 Extreme Goorse Axioms and their Implications

The paragraph presents a series of 'axioms' for Extreme Goorse, a tongue-in-cheek set of principles that satirize extreme approaches to software development. These axioms suggest that Extreme Goorse is faster than other methodologies, creates more problems than it solves, and is completely reactive. The speaker humorously explores the idea of committing code without regard for quality or standards, and the notion that deadlines are flexible in the face of client demands. The paragraph also touches on the concept of self-sufficiency in Extreme Goorse and the dismissal of traditional project management roles.

25:04

πŸ”„ The Downfall of Legacy Code and the Goorse Approach

The speaker reflects on the challenges of dealing with legacy code and the Goorse approach to software development. The paragraph humorously suggests that refactoring is unnecessary and that code duplication is preferred over abstractions and code reviews. The speaker also discusses the importance of embracing the chaos of a project and the potential pitfalls of trying to impose order on a Goorse-driven project. The paragraph concludes with a nod to the idea that success and failure are subjective, and learning from a project's challenges is a form of success in itself.

Mindmap

Keywords

πŸ’‘Agile

Agile is a software development methodology that emphasizes flexibility, customer collaboration, and rapid and adaptive responses to change. In the video, the speaker discusses misconceptions about agile, clarifying that it's not about speed but about delivering value sooner and being able to adapt to changes quickly. The term is used to critique the extreme interpretation of agile practices, such as constant sprints and stand-up meetings, which the speaker feels may not always be effective.

πŸ’‘Sprint

A Sprint in the context of agile development is a time-boxed period during which a specific goal is to be achieved. The speaker in the video questions the term 'Sprint' as it might imply a focus on speed, which contradicts the true essence of agile. The speaker suggests that software development is more of a marathon than a sprint, highlighting the need for long-term, sustainable effort rather than a quick burst of activity.

πŸ’‘Burnout

Burnout refers to a state of chronic physical and emotional exhaustion, often accompanied by feelings of cynicism and detachment. In the video, the speaker discusses how the pressures and expectations in software development can lead to burnout among developers. The speaker argues that doing meaningless tasks and feeling like a cog in a machine can contribute to burnout, rather than the pace of work itself.

πŸ’‘Extreme Goorse

Extreme Goorse is a humorous and satirical term used in the video to describe an exaggerated approach to software development, which prioritizes speed and getting things done over best practices, quality, and collaboration. The speaker uses this term to critique certain aspects of agile and scrum methodologies, suggesting that in their extreme forms, they can lead to chaotic and unsustainable work environments.

πŸ’‘Stand-up Meetings

Stand-up Meetings are short, daily team gatherings where each member reports on what they did the previous day, what they plan to do today, and any impediments they are facing. In the video, the speaker questions the effectiveness of these meetings, suggesting that they can sometimes be a waste of time and that more direct and informal communication methods might be more efficient.

πŸ’‘Kanban

Kanban is a visual project management method that involves using a board divided into columns to represent different stages of a process. In the video, the speaker mentions Kanban as one of the agile methodologies that can be perceived as miserable due to its focus on continuous workflow and the pressure to keep the process moving, which may not suit every individual or team dynamic.

πŸ’‘Refactoring

Refactoring is the process of restructuring existing computer code without changing its external behavior. Its purpose is to improve the nonfunctional attributes of the software, making it easier to comprehend, reducing its complexity, and increasing its maintainability. In the video, the speaker humorously suggests that there is no need for refactoring in extreme goorse, as the focus is on quick solutions and moving forward, rather than improving the existing codebase.

πŸ’‘Legacy Code

Legacy Code refers to older code that continues to be used and maintained, often without extensive documentation or following modern coding practices. In the video, the speaker mentions legacy code in the context of not questioning or changing working code, highlighting a common challenge in software development where existing, potentially poorly written code, is maintained instead of being refactored or replaced.

πŸ’‘Code Duplication

Code Duplication is the practice of having identical or very similar pieces of code in multiple places in a codebase. While it can sometimes provide short-term efficiency gains, it is generally discouraged because it can lead to maintenance difficulties and increased risk of bugs. In the video, the speaker sarcastically endorses code duplication as a feature of extreme goorse, emphasizing the focus on quick solutions over long-term code health.

πŸ’‘Documentation

Documentation in software development refers to the written descriptions and instructions that accompany a program or system to explain how it works and how to use it. The speaker in the video argues that in the context of extreme goorse, code itself should serve as the primary documentation, with comments and additional documentation being unnecessary. This perspective reflects a controversial stance on the importance of clear and comprehensive documentation for long-term maintainability and understanding of the codebase.

πŸ’‘Security

In the context of software development, Security refers to the measures taken to protect a system from potential threats and vulnerabilities. The speaker humorously downplays the importance of robust security in extreme goorse, suggesting that reliance on luck and a lack of interest from hackers are sufficient. This satirical comment highlights the reality that in some fast-paced development environments, security can be overlooked, which can lead to significant risks.

Highlights

Agile is not about being faster but delivering value sooner and in a constant manner.

The fairest definition of agile is to pretend that you're the king of England, valuing ceremony and tradition over progress.

Instead of daily stand-ups, a Slack chat could be more efficient for quick communication.

Agile is a reaction to developers not knowing how to communicate with each other effectively.

Sprints are just a time box for a certain amount of work to be done, not a measure of speed.

Software development is more like a marathon than a sprint, with repetitive efforts over time.

Burnout in the profession often results from meaningless tasks and a lack of progress.

The problem with agile is not the speed but the expectation of moving fast, leading to burnout.

Extreme goorse methodology is a humorous and exaggerated take on agile practices.

Extreme goorse suggests that errors only exist when they surface, implying a reactive approach.

In extreme goorse, there is no deadline, and the focus is on getting things done regardless of time constraints.

Extreme goorse does not respect standards, advocating for writing code however it solves the problem.

Extreme goorse is self-sufficient and does not require management or project owners.

The more extreme goorse is practiced, the more problems will be solved using it, leading to a chaotic system.

When using extreme goorse, if the system is abandoned for a trending methodology, the project may collapse.

In extreme goorse, the code is the only documentation needed, and additional comments are unnecessary.

Security is considered a secondary detail in extreme goorse, with a reliance on luck and lack of hacker interest.

Transcripts

play00:00

all right anyway Sprints the biggest

play00:01

mistake of software engineering I

play00:02

actually already agree with this take do

play00:03

we even need to read the

play00:05

article do we even need to I mean the

play00:07

man is scare quoting it just to remind

play00:09

you that you don't actually run you use

play00:11

words that sound like exercise but we

play00:14

all know you haven't left the chair in a

play00:15

long time damn I know harsh yes reality

play00:19

real sprinting towards failure okay

play00:22

let's talk a little bit about being

play00:23

agile yeah that's a that's a word you

play00:25

don't describe with Arch users and the

play00:27

Brazilian definition of the current

play00:28

state of agile generated extreme goorse

play00:30

methodology extreme goorse what the hell

play00:33

is okay I don't know what the extreme

play00:34

goorse is now you got me uh

play00:36

misconceptions the first thing is to get

play00:38

the common misconceptions out of the way

play00:39

agile is going fast by now we should we

play00:43

all should know that agile is not about

play00:44

being faster it's about delivering value

play00:46

sooner and in a constant Manner and

play00:48

being able to react and change course

play00:50

earlier I wouldn't necessarily say

play00:53

that's what agile's about I I'd say the

play00:55

fairest definition of agile is to

play00:58

pretend that you're the king of England

play01:00

and you love ceremony and that tradition

play01:04

trumps progress I thought that was the

play01:07

proper d definition yeah right like we

play01:11

all like to get dressed up in our robes

play01:13

we all want to have that nice hour and a

play01:15

half long ceremony for me to do the

play01:17

thing that I was already doing but to

play01:19

say I'm going to do the thing again and

play01:21

then I would love to have like a quick

play01:22

15minute

play01:23

check-in to tell you that I'm doing the

play01:26

thing that I'm doing like who like like

play01:29

real talk like like instead of like

play01:30

imagine you had a roadblock you could

play01:32

wait till the next day and talk about it

play01:34

and stand up or you could just find the

play01:36

person that you're roadblocked and go

play01:38

and talk to them like why do you need to

play01:40

tell everybody about your roadblock why

play01:42

not have like a little like like why not

play01:44

have a team slack chat where you're just

play01:46

like yo dog I got blocked by this and

play01:48

then instead of wasting everybody's time

play01:51

to be in a meeting someone an hour later

play01:54

could be like yeah hey guess what I've

play01:55

seen this before you know how I I can

play01:57

help you with this you know how crazy

play01:59

that would be to uh completely destroy

play02:02

standups and just have a slack chat

play02:04

every now and then hey I'm just saying

play02:06

I'm not a big fan of multi thousand

play02:08

15minute meetings you know that's my

play02:10

ideal that's everybody's ideal because

play02:12

it's better it just simply is better

play02:14

okay we can even have a stupid Channel

play02:16

called I got [Β __Β ] Dash your team name

play02:20

and then you put your problem in there

play02:22

and then everybody knows that that that

play02:23

channel is really important to listen to

play02:27

okay I'm just saying I just spilled

play02:30

coffee on myself we need to stand up I

play02:31

got to tell everybody about this oh [Β __Β ]

play02:34

I you know what I need to take I I need

play02:36

I need a moment here okay I'm going to

play02:38

talk about this for at least 15 minutes

play02:39

in stand up that I spilled coffee on

play02:41

myself today skill issue I'm dying of

play02:43

skill issues I'm literally dying in

play02:45

skill issues right now I pissed

play02:47

myself oh my God bro oh hell no man what

play02:52

the [Β __Β ] man get your ass on Sprint is

play02:55

doing all in the time slot okay so

play02:59

you're saying agile is not about being

play03:00

fast but it also means having Sprints

play03:04

questionable so you exist in society too

play03:07

it might have been an unfortunate term

play03:10

used by developers of scrum but it

play03:12

certainly doesn't help with all the

play03:13

agile as being fast people like to think

play03:16

Sprints however are just a time box for

play03:18

certain amount of work to be done you

play03:20

know the more I think about agile is

play03:23

agile just really a reaction to the fact

play03:25

that developers don't know how to talk

play03:27

to each other and we didn't have a good

play03:29

chat app to avoid talking to people when

play03:33

created you know like slack really

play03:35

wasn't there you know I was I was using

play03:37

Skype or some some nonsense I was

play03:41

literally using Skype at one of my jobs

play03:44

as a form of communication like we were

play03:46

practically on we're practically on AOL

play03:50

Instant Messenger sending each other

play03:52

messages yeah aim just shooting a little

play03:54

bit of aim at each other oh yeah hey hey

play03:57

everybody Boomer yeah boom

play04:00

the problem Executives push for agile

play04:02

and scrum because they think uh about

play04:04

being fast Sprints the biggest problem

play04:06

is that making software is not a Sprint

play04:09

it's a marathon yes well it's actually

play04:11

you do 400s over and over and over again

play04:13

until you die or create a marathon

play04:16

that's actually what software is is it's

play04:19

just individual individually the worst

play04:21

race you've ever done the 400 or you

play04:23

could say the 800 I think we could go

play04:25

back and forth on the worst possible

play04:26

foot RAC is either the four or the 800

play04:29

and you do that that over and over again

play04:30

until one of you die or you make a

play04:32

product unless you're not human you know

play04:35

that you cannot Sprint a marathon it's

play04:37

really bad uh hell most people can't

play04:40

even Sprint a short race and I'm also

play04:41

talking about software what the hell are

play04:43

we talking about the people resolve

play04:45

burnout plain and simple the profession

play04:46

loses a lot of good people because of

play04:48

burnout not to be confused with burn

play04:50

down charts also from scrum but somehow

play04:53

that doesn't generate any confusion for

play04:54

people the same people expecting more

play04:56

and more from developers so burnouts

play04:59

burnouts very interesting I don't think

play05:02

that moving fast is the problem or the

play05:05

expectation of moving fast is the

play05:07

problem for Burnout I I just don't think

play05:08

that that's what causes burnout I don't

play05:10

think burndown charts are what causes

play05:13

burnout I don't think any of those

play05:15

things are I think doing meaningless

play05:18

things is much easier to cause burnout

play05:22

right like if you feel like you're just

play05:24

like just such a cog and you're just so

play05:26

cogged out and that everything you do is

play05:27

just such a process and every last

play05:29

little point in your next three four

play05:32

five 6 weeks are all individually mapped

play05:34

out for you never to have any questions

play05:36

and then you're going to have to go and

play05:38

wake up every day and tell everybody

play05:40

what you're doing every single day in

play05:42

some stupid meeting where some guy's

play05:44

going to tell you all about his dog for

play05:45

the 17th time about how cute boots is

play05:48

well boots is just so cute you should

play05:50

see boots this morning boots is so it's

play05:53

just like you do that over and over and

play05:55

over again and man that's not that much

play05:58

fun like there's probably different

play06:00

archetypes of

play06:02

burnout I just don't think moving fast

play06:05

is the problem right like if you got up

play06:08

and your environment is changing all the

play06:10

time and you're constantly never making

play06:12

progress and it's an ever like it's

play06:14

literally like playing wow and just

play06:16

trying to level by killing uh pigs like

play06:18

that uh that starc that Starcraft [Β __Β ]

play06:21

it that South Park episode yeah you get

play06:23

burnt out pretty pretty much because

play06:25

it's not fun let's not blame agel for

play06:26

burn I'm not going to blame agel for

play06:28

Burnout I don't think that that's the

play06:29

fundamental problem like I don't think

play06:31

those things make burnout worse like I

play06:34

don't think agile itself leads to or

play06:36

doesn't lead to burnout let's blame

play06:38

agile for everything yeah I mean I I

play06:40

mean understandably agile agile is like

play06:43

that kid that always tells too much and

play06:45

you just want to punch him that's real I

play06:49

understand that the problem I have with

play06:51

just like whenever someone says like

play06:52

agile is actually great or agile can be

play06:55

you know like you're talking about scrum

play06:57

not agile the problem is is that scrum

play06:59

is an implementation of agile in some

play07:02

sense it's the attempt to codify what

play07:04

agile is into a thing into a set of

play07:07

things people can do and that becomes

play07:10

increasingly more and more difficult

play07:12

kbon is another one of these but kbon

play07:14

can feel equally as like Miserable as

play07:16

scrum is right it can be equally

play07:20

miserable because kbon in some sense I

play07:22

find kbon almost worse because it's just

play07:26

like you're literally so

play07:28

replaceable that you're just a cog that

play07:31

takes off the top of the list like

play07:33

that's your value is that you are just

play07:36

like how do we effectively Drive

play07:38

software engineering into what llms

play07:40

should do right it's just like we're

play07:41

going to break down the task as as small

play07:44

as possible and you're going to just

play07:45

shove through these things on just like

play07:47

a fire hose right kbon is NeverEnding

play07:50

torture absolutely and so it's just like

play07:54

my I mean my personal favorite way to

play07:56

develop things is that you get together

play07:58

with the people you're you're trying to

play07:59

develop with set a set of like goals and

play08:03

then you come back a week later and you

play08:05

talk about how are your like progress

play08:07

towards the goals going in any roadblock

play08:09

or anything you have in the way you

play08:11

reach out to the team members

play08:13

individually you don't you don't do any

play08:16

sort of planning you don't do anything

play08:18

of course that's agile agile that's the

play08:21

problem with agile agile has such a

play08:23

broad definition it's only part of agile

play08:25

it's one definition which is a team

play08:26

should set forward its own thing right

play08:29

that's it just set a goal as a team we

play08:31

set one goal one thing we want to make

play08:33

we want to improve the reliability of

play08:35

service X go and make it happen

play08:39

team right fail fast it's it's but it's

play08:43

not a Sprint like there's no there's I

play08:45

don't think check-ins or I don't think

play08:48

like tasks and extreme breakdowns work

play08:51

right if everybody's held accountable

play08:53

for what they do and every last person

play08:56

wants to see change and works hard you

play08:59

don't need need all these rules right

play09:01

and when people aren't doing it you're

play09:03

protective of the team and you talk to

play09:05

them you address issues and eventually

play09:08

you have to let them go like it's that

play09:09

simple I'm going to Agile these nuts

play09:11

across your face right such hard well

play09:14

you have to you have to create the team

play09:17

you have to create the team you want

play09:19

right anyone that thinks you can't

play09:20

create the team then that's a that's a

play09:24

problem this assumes Yes again you are

play09:27

the reason why teams have to be held

play09:28

accountable

play09:30

right you have to find people like

play09:32

yourself that hold people accountable

play09:35

and that's that like if you're if you're

play09:37

trying to do it in some top down way

play09:39

you're going to just land and scrum in

play09:41

Daily meetings and every this that and

play09:42

the other because now management has to

play09:44

come in and they're the ones that have

play09:46

to go through and do all this stuff and

play09:47

then it's just awful like I don't want

play09:49

that do you want that I don't want that

play09:52

but I love my scrub mommy well we all

play09:53

love our scrum Mommy okay okay but only

play09:57

one team gets a scrub mommy and that

play09:59

ain't me okay uh first off I don't

play10:02

believe that I I I don't believe this at

play10:04

all right here uh I cannot create my

play10:07

team and 30 million is on the line and

play10:08

contracts with deadlines are in effect

play10:10

if we fire people I have no one to

play10:12

replace them

play10:13

BS if you literally paid people a good

play10:16

wage a competitive wage whatever that

play10:18

competitive is for your area slightly

play10:21

better 5% better 10% better whatever it

play10:23

is you will literally have a load of

play10:25

developers knocking on your door right

play10:27

now saying pay pay me pay me pay me I'll

play10:30

do the work I'll do the work good and

play10:31

you you can just handpick right now

play10:34

great

play10:35

talent okay there are people desperate

play10:37

for jobs right now this I this idea that

play10:41

somehow like I mean I understand like

play10:43

tribal knowledge is really important and

play10:44

you can't just get rid of an entire team

play10:46

and then come back and create a new one

play10:48

right like that's not it's not that easy

play10:51

right people are really really really

play10:54

really wanting to work there's plenty

play10:56

like that is not right that is not

play11:00

like a thing okay all right anyways uh

play11:03

develop deliver deliver software not

play11:05

fast but with consistency the first

play11:06

thing people see in new Frameworks is

play11:08

how fast they can make a to-do app yes I

play11:11

hate to-do apps I hate to-do apps but

play11:14

that's not the reality for most of us go

play11:16

horsing quick and dirty to make a big

play11:19

bowl of Muddy pasta is okay for an MVP

play11:21

side project and a throwaway project I

play11:23

still don't know what go horsing is is

play11:25

this like a is this a Brazilian term

play11:27

that's being like transliterated

play11:30

across languages is there like is am I

play11:32

missing something uh but most of the

play11:35

time you'll be working for months on end

play11:37

on something what matters making one

play11:39

thing fast than slowing down on each new

play11:41

feature until you jump

play11:43

ship this yeah

play11:45

this this is actually pretty funny is

play11:47

that you slow the the the inevitable

play11:50

slowdown or decide to rewrite the whole

play11:51

thing dude holy cow oh so this must be

play11:54

okay so this is I see Axiom 8 Axiom 10

play11:57

this is funny cuz right when I said jump

play11:58

ship my next thought was or you just try

play12:00

to burn the ship and get a new one and

play12:02

then here you go rewrite the whole thing

play12:03

I might okay maybe extreme goorse is a

play12:06

I'm a fan of extreme goorse like is this

play12:10

is this HDMX mentioned is this what's

play12:12

happening right now okay as I was

play12:14

writing this post it came to my

play12:15

attention that extreme goorse is

play12:17

commonly known only by Brazilian deaths

play12:19

yes I literally I first off Brazil

play12:22

mentioned can we get a Brazil mention

play12:23

can we just get I just just just so you

play12:27

know Brazil was just mentioned okay and

play12:30

I I don't think people are are are

play12:32

experiencing how amazing that is

play12:36

processess right Brazil mentioned this

play12:38

is fantastic horsing the man's horsing

play12:41

around but not enough around the world

play12:43

this was made by who knows when by who

play12:45

knows who it's a little outdated in the

play12:47

writing I'll refactor as needed but you

play12:48

will see it's Timeless C axium 14 uh and

play12:52

re and relevant to what I was saying

play12:54

disclaimer this is basically not a to-do

play12:56

list it's a funny it's let's see it's

play12:58

funny as a meme but as I like to say if

play13:01

all you do are things from memes then

play13:03

your life is a joke it's real take you

play13:06

know those people that always are like

play13:07

ironic on the internet and they're and

play13:09

they're and they're

play13:11

continuously just like saying [Β __Β ]

play13:13

that's like really on the edge like real

play13:16

Edge Lords and they're just constantly

play13:17

being like dude it's just a joke bro but

play13:19

they only operate in that mode you know

play13:22

what I mean and you're just like are you

play13:25

sure you're living ironically or are you

play13:27

just like is that just you

play13:30

it's this this is who you

play13:32

are uh there were some translations out

play13:35

there but I translated them here by

play13:37

timeing uh let's see by trying to update

play13:39

things and make it more easy uh make it

play13:40

more sense today enjoy but don't follow

play13:43

it little note people usually uh just

play13:45

read x g Extreme goorse as goorse all

play13:50

right the goorse manifesto by the way I

play13:51

typically don't like to read manifestos

play13:54

um just the idea the whatever reason the

play13:58

word manifesto gives me the heebie

play13:59

jeebies okay I don't I don't I don't

play14:01

like it but we're going to do it anyways

play14:03

here we go if you had to think it's not

play14:06

extreme

play14:07

goorse in extreme goorse you don't think

play14:10

you do the first thing that comes to

play14:11

mind there's no second option the only

play14:13

option is the fastest

play14:16

one there's this weird part of me that

play14:18

likes and hates this all at the same

play14:20

time I feel I feel like a mixed drink

play14:22

right now you know what I mean I can't

play14:25

tell which part of me loves this and

play14:26

which part of me hates this

play14:30

you know what I mean and the hard part

play14:32

is is that I'm thinking about something

play14:34

and it just told me not to think let Tim

play14:35

Cook

play14:37

already okay so so extreme goorse can

play14:41

also be replaced with GSD that's the

play14:43

American way to say it which is get [Β __Β ]

play14:45

done um yeah for the most part I

play14:48

actually genuinely agree with this

play14:49

whenever I'm prototyping or kind of

play14:50

specking out something or just trying to

play14:52

investigate how something works like

play14:54

this is what I do I don't even try to

play14:55

make it pretty at all I I'm building it

play14:58

just to get [Β __Β ] done come up with some

play14:59

ideas and then maybe make something that

play15:01

makes sense later on uh there are three

play15:03

ways of solving a problem the right the

play15:05

wrong and the extreme goorse which is

play15:07

like the wrong one but

play15:14

faster I'm not sure if these are great

play15:15

axioms extreme goorse is faster than any

play15:18

other methodology of software

play15:19

development you know okay okay the more

play15:23

extreme goorse you do the more you'll

play15:25

need to do it for each problem solved

play15:27

using extreme goorse about seven more

play15:29

will be created but all of them will be

play15:31

solved using uh extreme goorse extreme

play15:33

goorse tends to Infinity I'm glad we got

play15:35

like the limit definition of Extreme

play15:38

goorse as time goes as time goes to zero

play15:40

is infinity react mentioned is that what

play15:44

is that what we're seeing zoo zoo

play15:47

mentioned extreme goorse is completely

play15:49

reactive erors only exist when they

play15:51

surface so that's kind of a funny phrase

play15:53

they're using there erors only exist

play15:55

when they

play15:57

surface which by all definition is the

play16:00

only ways in which errors become

play16:03

known which you can be

play16:05

proactive by trying to look at the

play16:08

surface so is it reactive or proactive

play16:11

extreme goorse accepts everything solved

play16:13

the problem compiled commit that's it

play16:16

always commit before updating if [Β __Β ]

play16:18

happens your part will always be correct

play16:20

and your colleagues can go [Β __Β ]

play16:25

themselves I think I'm a huge fan of I

play16:27

think I'm a huge fan of goor right now

play16:29

extreme goorse goorse I think I I'm I'm

play16:32

in on this one I'm in on this one

play16:33

Extreme goorse has no deadline the

play16:34

deadlines set by your client are more

play16:36

are mere details you always uh be able

play16:40

to implement everything in the given

play16:41

time even if it involves accessing the

play16:43

database with Shady

play16:45

script I mean I I've worked that job

play16:48

I've been at this job I know this job I

play16:51

feel this

play16:52

job be prepared to jump ship when it

play16:54

starts to sink or blame someone or

play16:56

something else for those who use extreme

play16:59

go horse one day the ship will sink uh

play17:00

the more time passes the more the system

play17:02

becomes a monster the day the house

play17:04

Falls it's better to have your LinkedIn

play17:06

updated or have something to blame be

play17:09

authentic extreme goorse does not

play17:11

respect standards if you write code

play17:13

however you want let's see write code

play17:15

however you want if it solves the

play17:16

problem commit and that's it isn't that

play17:18

pretty much I mean I mean that's

play17:19

actually just modern-day coding this is

play17:21

this is actually just like this is

play17:22

actually just like this is just coding

play17:24

right I I hate to break this to you but

play17:26

this is how everybody writes code when

play17:28

somebody tells you something is cleaner

play17:31

it's not cleaner it's because they like

play17:33

it

play17:34

differently okay some people like their

play17:36

cucumbers pickled like that's just a

play17:37

fact of life 10 there is no refactoring

play17:40

only rework if [Β __Β ] happens redo a quick

play17:43

extreme goorse that solves the problem

play17:45

the day the rework involves rewriting

play17:47

the entire application jump ship uh and

play17:49

the boat will sink it will sink it

play17:51

actually will sink I have rarely seen a

play17:53

rewrite work and when a rewrite happens

play17:55

I've just never I've never seen good

play17:57

things about rewrites extreme goorse is

play18:00

completely uh anarchic uh the figure of

play18:03

a project manager is completely

play18:05

disposable there is no owner everyone

play18:07

does what they want when problems and

play18:09

requirements arise you know this isn't

play18:12

far from bad advice because I mean I

play18:14

understand like this whole list is like

play18:15

supposed to be bad advice but there's

play18:17

accidentally good advices in here in the

play18:20

sense that everyone should try to solve

play18:23

a problem or everyone should try to like

play18:26

do what they think is best when problems

play18:27

or requirements arise rather than having

play18:29

formal meetings about everything like

play18:30

I'm actually on that team that there is

play18:33

something like sometimes these bad

play18:35

advices are actually accidentally okay

play18:38

always delude yourself with Promises of

play18:43

improvement I mean I agree with that

play18:45

okay I agree I agree I mean I I I agree

play18:48

tweet material putting to do in the code

play18:50

as a promise of improvement helps the

play18:52

extreme goorse developer not feel

play18:54

remorse or guilt for the [Β __Β ] for the

play18:55

[Β __Β ] they made of course refactoring

play18:57

will never be done C M 10 uh extreme

play19:00

goorse is absolute it does not cling to

play19:03

relative things time and cost are

play19:04

absolute quality is totally relative I

play19:07

actually this is accidentally true I

play19:09

know this is supposed to be a meme but

play19:10

this is accidentally

play19:12

true uh never think about quality only

play19:15

let's see only about the shortest time

play19:17

uh the solution can be implemented in

play19:19

fact don't think just do it that's Axiom

play19:21

one you should have cited Axiom one okay

play19:24

if we were proper here you would have

play19:25

known that that that that that if you

play19:27

had to think it's not extreme goorse you

play19:29

would have known that but you clearly

play19:30

didn't you forgot clearly whoever wrote

play19:33

it was not thinking uh extreme goorse is

play19:35

timeless scrum extreme programming all

play19:37

of this is just a fat extreme goor does

play19:39

not cling to fads of the moment that's

play19:41

for the weak Extreme goorse has been and

play19:44

it will always be used by those who

play19:45

disregard

play19:49

quality extreme cor is not a workaround

play19:52

oh let's see on Extreme goorse is not

play19:54

always workaround oriented programming

play19:56

many workaround oriented programming uh

play19:58

requires a high level of thinking but

play20:00

Extreme goorse does not see axm one

play20:03

thank you translator node in the

play20:05

original it uses garia oriented

play20:07

programming since I understand some

play20:09

people will know what garia is it's more

play20:12

encompassing term than just hack or

play20:16

workaround is garia something like

play20:19

circumference is that like fairish it

play20:22

means ass doesn't it garia is like

play20:24

Brazilian

play20:26

macgyverism appreciate that anyways uh

play20:28

don't try to swim against the tide if

play20:30

your colleagues use extreme goor for

play20:32

programming and you are the stickler who

play20:34

likes to do things properly forget it

play20:35

for each design pattern you use

play20:37

correctly your colleagues will generate

play20:38

10 times more rotten code using extreme

play20:40

goorse extreme goor is not dangerous

play20:43

until a little order arises the axium is

play20:45

very complex but it assumes the projects

play20:46

using extreme goorse is in the midst of

play20:49

chaos don't try to add order to extreme

play20:51

goorse uh it's useless and you can waste

play20:53

precious time this will make the project

play20:55

sink even faster don't try to manage

play20:57

extreme goorse it is self-sufficient

play21:00

just like the chaos you know there's

play21:01

actually an accidental piece of wisdom

play21:03

in this one as well which is like if you

play21:05

came into a project it had one month to

play21:08

ship and it's just absolute

play21:10

craziness like do you think you can

play21:12

just say well this is crazy we better

play21:15

rewrite this right sometimes you do just

play21:18

have to embrace the chaos sometimes

play21:20

you're like this C this is crazy I'm

play21:22

going to make a script that does like a

play21:24

full integration test on this and I'm

play21:27

going to hope everything goes great you

play21:28

know like you just sometimes Thanos

play21:30

mentioned sometimes you just got to go

play21:31

for it you know what I

play21:33

mean just give the gasoline for the fire

play21:36

you called exactly chaos CL Charlie yeah

play21:40

exactly let's see uh goorse is your ally

play21:44

but it is vengeful as long as you want

play21:47

goorse will always be on your side be

play21:48

careful don't abandon it if you start a

play21:51

system using goorse and abandon it using

play21:53

trending methodology you're [Β __Β ]

play21:55

goorse does not allow for refactoring

play21:56

C10 and your new full of Frills will

play22:00

collapse and at that time only goorse

play22:03

can save you if it's not working don't

play22:05

or if it's working don't touch it never

play22:07

changed let alone question working code

play22:10

I mean this is every piece of Legacy

play22:13

code that has ever existed that's a

play22:15

waste of time especially since

play22:17

refactoring doesn't exist C10 time is is

play22:21

the gear that moves goorse and quality

play22:23

is a negligible detail testing is for

play22:25

the week if you put your hands on goorse

play22:27

system you better know what you're doing

play22:29

if you know what you're doing why test

play22:31

testing is a waste of time if code

play22:33

compiles that's enough get used to the

play22:36

feeling of eminent failure failure and

play22:37

success always go hand inand and in

play22:39

goorse it's no different people often

play22:41

think the chances of a project failing

play22:42

using goorse are always greater than it

play22:44

being successful but success and failure

play22:45

are a matter of perspective did the

play22:47

project go down the drain but you learn

play22:49

something then it's a success for you

play22:51

the always positive Bob ra style I love

play22:54

it uh the problem is yours only when

play22:56

your name is in the G blame never put

play22:58

your hand on a file whose author is not

play23:00

you if a team member dies or is sick for

play23:02

a long time the boat will sink in this

play23:04

case use Axiom a oh my goodness more is

play23:08

more with goor you thrive on code

play23:10

duplication code quality doesn't matter

play23:11

and there's no time for abstractions

play23:13

code code reviews or refactoring time is

play23:15

essential so copy and paste

play23:18

quickly again there's so much accidental

play23:21

almost wisdom in here almost it's like

play23:24

so close isn't it funny that what is

play23:27

actually a good idea can be masqueraded

play23:29

as such a bad idea isn't it funny how

play23:32

that works like that you could like

play23:35

that's it's actually one of the dangers

play23:36

it's I think it's one of the reasons why

play23:38

really bad ideas tend to crop up in

play23:39

software is that I can make such a straw

play23:43

man such as this and sell it as a reason

play23:47

why you should abstract everything and

play23:49

it's like I've just created this bogey

play23:51

man that's like impossibly

play23:54

scary this is why we should do something

play23:56

else and then the next thing you know is

play23:58

you find yourself just with Builder

play23:59

factories coming out the ass it's

play24:02

crazy right uh not accidental we now we

play24:06

we know it's the right way it's uh like

play24:08

it's grug programming not Grog Grog is

play24:10

something different anyways the code is

play24:13

the documentation I actually do agree a

play24:14

lot with this General approach uh in

play24:17

goorse the code is the only

play24:18

documentation needed comments and

play24:19

additional documentation are just a

play24:20

waste of time if someone can't figure

play24:22

out how the code Works they shouldn't be

play24:23

working on it cm20 um again this is so

play24:26

close to being true I actually really

play24:28

dislike 99% of code comments one of my

play24:31

favorite code comments was a code

play24:34

comment at the top of the file and just

play24:35

said hey I had to make a lot of

play24:37

shortcuts in this file I want you to

play24:39

know that beforehand that these two

play24:41

tickets and jro were the reason why I

play24:43

did what I did I'm not happy about it

play24:46

but I did it and I am happy about it the

play24:49

bug was fixed this code is [Β __Β ] sorry

play24:53

not

play24:56

sorry that was at Netflix it was

play24:59

fantastic one of my favorite developers

play25:00

I've ever worked with put that code

play25:02

comment at the top it was amazing it was

play25:04

perfect it was exactly correct the code

play25:06

was

play25:07

[Β __Β ] I couldn't be upset because I saw

play25:10

why it was and I just kind of agreed I

play25:12

was like yeah you know you're right

play25:14

you're right you're right the code is

play25:17

horse crap the go the code is goorse but

play25:20

I'm not sure if you could give any you I

play25:21

don't I don't know if you could do any

play25:22

better in goorse a security is a

play25:24

secondary detail it's a waste of time to

play25:26

implement robust security C5 and S trust

play25:28

in luck the lack of interest from

play25:30

hackers C

play25:33

ax8 it's pretty good this is pretty

play25:37

good uh you know it's weird

play25:40

because I can't tell what part of this

play25:45

was satire and what part of

play25:47

this wasn't satire you know what I mean

play25:52

like I can't tell I honestly can't tell

play25:55

cuz like this right here feels like it's

play25:58

meant to be true right that agile is not

play26:01

about moving fast it's about delivering

play26:03

value sooner and in a constant Manner

play26:04

and being able to react to change uh and

play26:06

change course earlier like that feels

play26:09

like you're you're trying to give a

play26:11

legit definition of

play26:14

agile and then just tosses

play26:18

in in goorse you don't

play26:24

think

Rate This
β˜…
β˜…
β˜…
β˜…
β˜…

5.0 / 5 (0 votes)

Related Tags
Agile MisconceptionsExtreme GoorseSoftware EngineeringDevelopment HumorProject ManagementScrum CritiqueKanban ComparisonBurnout DiscussionTeam DynamicsCoding Practices