All this hostility aside, I feel sorry for you if these complaints are actually legit from your workplace. You should look for another job. It sounds like yours sucks.

It is the 4th time I am in a SCRUM team now. I am in an escape route. Good developers already left, I probably will be next.

No. Give him the same user stories as your highly successful SCRUM team. That is his general direction he is going to head for. Don't expect him to follow the user stories, it is the end result that counts.

No pre-planning no scheduling, no fixed deadline. Just a deadline around your next demo but give him wiggle room to delay a few days, no code review, no stand-up meeting. He builds from withing the code towards the desired result.

He will be far more productive when he is in "the zone" and can focus at the best problematically path to reach that end-goal that encompasses all user stories. He will focus on hard things when he feels good and only do boring stuff when he feels in no not so good day. And that can change by the hour.

He is going to use AGILE how it is mean to be, without the slowdown.

He is faster because he does not get slowed down with internal communications and endless debates and team meetings. He is faster because he does not have to also know the other unimportant things for the current goal he needs to have right now. He is also faster because he can test multiple results in one test, while the SCRUM equivalent would be every test for every user story.

The issue here is that not every developer will be this effective. And you must also trust that developer that the outcome will be a success. But when the developer has a track history of near zero bugs and lots of success rates then you must trust this knowledge.

Don't worry, at the end when the demo happens, you will still to test it the SCRUM way user story by user story. And you will still have the same unit tests and builds/deployments. Bit it will be highly optimized code, more reliable, less bugs and easier deployable.

But but but, how about transfer of knowledge? That is a none issue since good developers can jump into any project, focus on it and they will be up and running in a very short time.

Too scared to do the test and discover that your productive agile team can't keep up with a single developer that is not confined into the SCRUM restrictions?

Just take the challenge, take one of your "best" developers and let him work "outside" the SCRUM team. All you need to do is answer his question "What do you want?"

Explain to me, please, what are the restrictions of SCRUM that need bypassing?

If you were a developer you would not even ask such a question. The overhead 90% that SCRUM creates and prevents you from doing your job. You literally waste productivity by "opening the road- put in the red cable, close the road. Open the road, put in the yellow cable, close the road. Open the Road, put in a green cable, close the road"

I am going to repeat the challenge: Take one good developer let him do the exact same job as the complete SCRUM team and he will outpaced the SCRUM team, and produce better code. I am not asking you to believe me. Dare to do the test!

SCRUM is a series of restrictions on how your product manager is permitted to interfere with you building great products.

No! SCRUM causes so much overhead that it prevents great products to be developed. Your so called velocity is only an illusion number that makes you think that your are productive. That number is solving problems that is caused by SCRUM in the first place.

May I give you a clue what good developers can do? Good developer create code in such a way that they have absolutely no problem when a product manager comes in with last minute changes.

It is a big giant money making business to sell SCRUM teachers and certificates. It is the equivalent of the "Pay lots of money for this special class that will make you a billionaire in 6 months"

In addition it is also a big business for companies that cell these AGILE tools. You need to pay enormous amounts of money on tools that solves problems are caused by AGILE working.

With SCRUM you lose 100% productivity, but by buying these special tools you can increase your productivity to 10% again. At the same time with SCRUM your team works at 120%.

The madness in AGILE is that you need 8 people 2 weeks to do the exact same job as one good developer in 1-2 days.

Because we come from a time where we used 90% of our time on creating great products. Now we use 90% of our time to develop tools to bypass the restrictions imposed by SCRUM and to recover the wasted hours we lost on stupid SCRUM meetings.

Pragmatically, there is also much about the inefficiencies of object-orientation that workplace Marxism has come to love. The fact that object-oriented systems suffer a fundamental lack of modularity goes a long way to justify the collective code ownership.

This is wrong, you can perfectly use functional programming techniques within an OOP framework. That is what I do, I use best of both worlds to develop code that is almost bug free and reliable for years to come.

The reason why OOP seems to fail is because people use it wrong. The models are built the wrong way. They use it as some kind of glorified namespace and object layers that is only 1 dimension deep.

So instead of hiring a few talented engineers, our dear Leaders take advantage of cheap labor pools to hire as many interchangeable mediocrites as possible. In spite of all reason and evidence, they continue to insist that 9 women can make a baby in one month. To them it would be a contradiction to believe otherwise.

Amazingly, when engineers under pressure annihilate architectural constraints as a side-effect of hurriedly patching in new features, this is called having ‘high velocity’. Appallingly, this type of ‘velocity’ is the main measure by which engineering progress is judged in Agile. Agile basically turns software companies into Soviet shoe factories.

This is spot on.

Great article!

It only works on certain files, like 4 GB of zero's. It probably even works on 2 GB of zeros, hey 1 GB of zeros can work too I think.

We are working AGILE now, everyone must know everyone's code so picking a language is not important. Just learn 10% of any language and off you go.

You sir are evil. You did not provide a solution that he can copy and paste from.

But what exactly are these skills? What does maintainable code exactly mean, that a software developer candidate needs to have expertise in? How can be a codebase’s resistance to change kept low, so that more and more features can be added without interruptions, and more and more developers can be hired to add new features even faster, and less and less full rewrites are needed, every couple of years?

Adding more developers doesn't work, all you do is cripple the team even more.

I heard someone here as example that SCRUM is like climbing a tree and expect that when enough people climb trees that you will get to the Moon.

I also heard on a Youtube discussion that AGILE is like running a marathon by having your team gave 100 meter sprints every 1 week. That team never ends the marathon, they burn out or leave the company.

The only thing AGILE do is giving the illusion that your team is productive but in reality they are wasting 90% of their productivity time on senseless meetings, planing, and creating spaghetti code that will fail the project.

To give an idea how deep the SCRUM madness gets: Imagine that you have 3 contractor workers that has to wire some building.

• Contractor A opens the road, puts in the cable and closes the road.
• Contractor B has to wait until contractor A has closed the road before he can open the road put a cable in and close the road.
• Contractor C has to wait until contractor B has closed the road before he can open the road put a cable in and close the road
• Contractor A suddenly discovers at the demo that reds are red and it turns out that Contractor C has damaged the wires of Contractor A.
• Contractor A has to reopen the road to emergency repair the wiring and close the road again.
• Contractor B now suddenly discovers that Contractors A emergency repairs now sens false sensory data to their wiring system.
• Contractor B has to reopen the road, introduce some noise reduction filters and close the road again.

Look at the madness of wasting precious time and energy that could have been used for development instead.

One guy could have opened the road, put in all cables, cross checked of the cables are not damaged or interfere each other and only after he tested then he closes the road.

I challenge the companies to do this simple test. Take one good developer, and let him implement the same features as the complete scrum team. But no planning, no meetings, not predefined order no daily meetings, let him ficus on the work and stand back. That one guy replaces your complete SCRUM team and the end result will be better!

Moreover, there are actual methodologies that build on this idea of perpetual incremental improvement. Agile and lean methodologies require codebases that can manage and deal with change from day one, from the first line of code. That are written for change.

They suck at change! Agile has become a mega big industry of certificates where scrum teachers gets rich by promising companies eternal wealth by firing half of their developers and replace the other developers by low wage developers.

There is nothing Agile in Agile development, been in and out of Agile development and the development speed and development quality really sucks.

And the sad thing of all, you create a generation of developers that does not know that all their projects can be done faster, easier and cheaper. being brainwashed that AGILE is the only way, but it is not. It is the stupidest way, based on religious believe that AGILE is the lord and savior!

I have seen so many rewrites and they always end up with the exact same program but with different problems. How many times I have heard: "We are going to rewrite it from scratch, but this time good...." and then fail yet again.

The key to good development is to choose what you want to do and then bend the code around it. Never bend the solution around the technology because some design pattern can't handle it! Say fuck you to the design pattern and solve the issue. It will freak out the code monkeys but who cares? Your product matters. the end-user matters, the support team matters.

Sticking to precreated stuff and design patterns doesn't make you a good developer it only turns you into a code monkey.

Also by using someone else's code you yet again create some cloned variant of the exact same application. You will never become a good developer because you do not have the ability to create something new out of thin air. As a developer you will become obsolete pretty soon replaced by a schoolboy that just graduated from school.

I started to listen to the guy but couldn't stand it anymore in the crap he was spouting.

If you are a seasoned developer. I mean a developer with tons of experience and a stream of successful projects then you realize that what this guy is saying, is that you use up 90% of your development resources on something that never was a problem in the first place.

Your projects becomes so complex with additional crap for these unit tests on all levels that no understand the code anymore. They just change something and pray that it turns green. If it turn red then they are going to wiggle something hoping that this time it turns green. When it is green then they assume that it is not going to wipe out civilization by some yet unseen bug.

The only things these green unit tests does is is make the manager happy by showing that it is all green. If these manager would realize what is below that shiny green light I think they will live in terror.

There is nothing AGILE in the AGILE process, just a a placebo to find excuse why your projects development are so slow and keeps on failing.

I love Visual studio but it comes with telemetry and spywere even in your "Hello world" console.

Microsoft adds secret snooping codes into C++ Binaries Visual Studio 2015, when caught says it is for debugging: https://www.techworm.net/2016/06/microsoft-secretly-adds-snooping-codes-c-binaries-visual-studio-2015.html

I just lost my eye sight.

Your wording fits perfect how I feel.

It has been broken for at least a decade.

The code quality and overall architecture are the responsibility of the lead developer,

Not many good lead developers exist anymore. And with that, dying off good developer that can learn from these lead developers.

The problem is that boot camp students overwhelms the good developers to a point where the good developers are outnumbered and replaced. So when you get rid of the only people that can Tapdance around your complete team and still end up delivering a working project then no one can call these people out anymore that they are doing it all wrong.

Right now I see this process happening at a client where I work. The good developers already started to jump ship, I am probably next. The last thing you want to be associated with is a project that will end in massive failure. Very bad for your resumé.

I have one to add: Don't use "design patterns"! "Design patterns" gives the false impression that you have control but in reality it makes you code harder to understand, harder to modify and you end up with a ergonomics disaster.

Be creative and design your own design pattern based on what you need to make. And this is very important in a game. Using design patterns makes you game exactly as bad as the competition. However if you use your creative mind, you will create a mechanism that will outperform the competition and do things they can't.

Just look at the current state of the games. They have flashy graphics but are completely worthless. They are just the exact same clones as the competition with the only difference of the background scenery.

Yes, but I open the discussion to have more ideas and to trigger more people to create their own variant.

We should not have one discussion how to pollute the privacy data, it should be flooded with many different people all talking and discussion how to do it. Variation is key here so the other people gets enough interest to start their own variant.

It should become so on the top of discussions so that even search engines will show people how to hide their privacy by noise.

People were smart in those days. LOL

You need to extend to add profiles and timings.

• Working people only log in to the PC at certain times. During lunch break, after they come home......
• Increase or decrease Internet usage depending on the time, weekend, day time, holiday..... Just pretend that it is a real human.
• Males could surf for porn when the wife has gone to bed.
• Avoid "Trump" keywords if you want to hide the fact that you are a Trump supported, increase your search on "Hillary"
• Randomizing mechanism so when 100 people use your profile, it does not show up as a spike in the analysis tools by the government.

More important don't use an app, but create scripts that can be copied and pasted by people without having to download source code. Everybody can have Python, and is harder to track a script. Even better would be distribute the scripts through message boards so there is no single point of entry that can be tracked. If you have it on github then the government can look who downloaded it.

Identity can be fakes with fake browser history. What's the point in inventing all these AI chat bots, if you don't use them to pollute the tracking histories and bring back privacy?

Yep you can take any identity you want.

I have noticed recently that the Internet is forgetting who I am. Up until a few years ago "the Internet never forgets". However with all these privacy tracking, telemetry data, the big companies gets so overwhelmed that they have to filter the data and interestingly enough all the data I find on myself are outdated, wrong and unusable. Even though my name is still out there it gets corrupted with data that they try to complete but is completely wrong.

The added bonus is that big data is so vast that big companies can't even verify anymore if their data is actually valid or pure corrupted and fakes.

First there was fake news, now there is fake browser history. LOL

The interesting idea is to generate fake Internet history that pretends that you are a choir boy that goes to church every Sunday and live at your mums basement while in reality.....

EDIT: we also need to generate fake Siri/Cortana requests.

No. Mainly for troubleshooting and law enforcement.

Which becomes useless once people start to generate fake browser histories. You can become invisible when there is so much data noise generated that your main signal is buried in.

A bit like firing shaft to jam the radar signals that are homing onto you.

The fact that it is in the open that governments and big companies are spying on you, their data becomes useless for finding real criminals because they will jam their signal.

Yes we would have the same zero privacy however we can induce so much noise in our privacy tracking data that it become worthless to the companies and unsellable. Even worse it would cost them a lot of bandwidth ans storage space to store the worthless data.

The ultimate payback, it cost them more than it is worth the data to collect.

I think it all depends on the region. But also realize if something is popular, it also means that you have tons of competition that are probably cheaper than you.

What I do is I learn the mainstream enough to know what it is all about and to pass a HR selection. The moment that I need to apply for the job I already have a head start and can focus to learn it fast prior for the interview.

The key in becoming a good developer is that you can adapt fast. never that you excel in one framework or language. Learn to make your brain placid enough to quickly to unlearn things and relearn something new in a week or a month. C++ took me a month to get used to the rest normally one week or so.

I dare you to do the test. Take one of your good developers and take one AGILE team and let them do the exact same work in parallel. That single developer will beat your AGILE team and be even more agile than you AGILE team.

Don't believe me, just try.

Yes I will keep complaining with it because it is been sold as some miracle cure while in reality it is the biggest cause of project failures the last 3 years. Look around you many applications have been deteriorated in pure crappy and ergonomics disastrous applications.

And no you don't have to rewrite the application from scratch. Just stop forcing your best developers follow this AGILE methodology and let them do their jobs. They will speed up 10 times. When I look at what I develop, what I normally do as one is now a complete team of 8 people. The team of 8 could have developed 10-80 times more but you cripple them with this stupid AGILE methodology.

I personally like Scrum because it eliminates bureaucracy and gives a lot of freedom to developers.

No it is not, it is one giant bureaucracy. The freedom on the developers is just an illusion in reality it slows them down.

Very nice overview.

Just one note, RS-232 still exists and is still used a lot. In Arduino projects and probably most USB device where there is an FTDI chip or FTDI-like clone that converts USB data to serial data for internal communication.

Impressive.

The only difference is, its not taboo for developers to speak to managers about the incompetent male whereas it is considered taboo to speak against incompetent women.

I could not have worded it better myself.

As I told my GF, the developers world is one of the harshest and brutal career you can take. It takes 24/7/365 effort to keep your knowledge up to date.

Forcing everyone to learn coding, and forcing women to choose for STEM will put all these people that are unfit into a burn-out within a few years.

On top of that software developing is always disappointing because you work very hard and no one understands what you do. And one of the weird things is that code that looks elegant and easy to understand is actually the hardest to create. Managers don't get impressed if these 100 readable lines is all you did in the last week. They get impressed when the idiot created 10,000 lines of code all linq statements no one understands.

The thing about programming is that in a proper shop there's zero room for emotional arguments and ego. Facts rule everything.

One would think so but I have met a lot of developers that have an ego the size of a planet. And somehow these people befriends the managers and they stay in the company for many years.

It is amazing how managers gets so easily fooled by these big ego and victim blaming developers. I have always wondered why, but I think these managers lack technical knowledge and don't want to admit that they don't know what you are talking about. So they lock onto the guy that acts the most cool.

She's taken every small low risk project and turned them into $500k-$1000k fiascos when the project estimate was for less than 1 month for 3 people including her. Her 1 month projects are always finished about 9 months later and clients usually refuse to take delivery or would have to be coerced into taking delivery yet she still works there after screwing up 3 projects pretty badly since i've been working with her.

Sadly enough I also have witnessed this with males. Sometimes you wonder wtf is wrong with the managers for keeping them. The answer is mostly because he is such a social good guy.

Also the victim playing, I have seen many males play the victim card why again their projects refuse to work. They always blame it on something else, like the wrong Windows service pack installed, the wrong version of the OS, the wrong firmware on that notebook, the wrong version of Flash installed. Must be 13.0.1.6532 and you installed 13.0.1.6522..... And fro some strange reason managers keep these idiots destroying every project they get in their hands for years.

Everything you described is all about the people, not the process. The process can't hurt anyone, it can't fire anyone, it can't yell at anyone.

But the process can suck big. Do you know that "The process" has brought my productivity to 10%? Not only did it kill my productivity I am forced to deliver buggy code because of "The process"

I've seen people who didn't care at all about design guides and it was a nothing but a tangled mess.

I have seen more code that did follow the design guides that are completely unusable. I can remove 75% of most programs that are following the design guide and I guarantee you that they will work faster, near bug free, easily deployable, easy modifiable, easy documentable, easy testable and on top of it all "user friendly".

And on top of that, I probably do it in half the time your developers would take, guaranteed success, and developers fresh from school can easily understand the code, modify it and take over.

Because you want to ensure that you always pass the majority of tests, you tend to think about this when you change and extend the program. You therefore are more reluctant to make large-scale changes that will lead to the failure of lots of tests. Psychologically, you become conservative to avoid breaking lots of tests.

I see this happening in AGILE teams. Teams dead scared to change anything because they risk that they fail the sprint. And good developers are held back to change too much because it might break something. So months later the software is in a worse crap than before.

The failure in unit testing as the SCRUM is relying on is, that you get a false sense of security/ Below the hood you may have 2 errors compensating each other and you don't realize it. Developers never do any effort to understand the code what is behind the tests. They just blindly assume that the test works perfectly and is to be trusted. However to get to the sprint deadline developers could disable the unit test, they will fix it after the demo. But they forget.

The idea of TDD is modeled on good developers as AGILE, however it gets abstracted to the extreme in such a way that even the developers they modeled it on will fail. Good developer invent new wheels and design patterns depending on their needs. They say f*ck you to imposed design patterns and design rules.

It is electronics but the way she is explaining is really fun compared with the boring courses.

I always avoid recursion at any cost. Most of the time you can rewrite the code without recursion.

Recursion is hiding the code constructs and is incredibly hard to debug. You may understand it at this moment, but as your program ages, languages change, syntax change, it is going to kick your ass big.

My advice: avoid them.

AGILE/SCRUM is not the way, it causes results that is rotten to the core with a shiny surface.

Secure software must be designed from bit one. And it takes time to get good results and takes masters. And you can't rush masterworks it takes time to age.

Also good software is better developed with a small team that gets the focus without a rush to get that sprint deadline. The obsession to focus on user stories alone, prevents good developers to change the underlying structure when they discover a design flaw. Let them do their job and trust what they produce.

Full stack developers tend to produce bad quality end-results. I could be regarded as some full stack developer because I can jump on any level you throw at me, but when I become good at one thing I lose experience at the others.

It is wrong to assume that when you understand 7 levels that you become 7x times better. In reality you become 1/7th better because you are just one person. It will actually become 1/10th because of the overhead.

Being full-stack also comes at a cost. Your s a developer doesn't have good experience at any level. You become just average just like all other code monkeys. There is no pride anymore in the work that you created because another code monkey will probably destroy the quality and replace it with a broken system. So you stop caring about the code you produce and the quality goes down. Projects fail.

Code monkeys can appear good for a company since they are cheaper than experienced developers and can be easily thrown away and replaced. But the cost savings are short lived since it guarantees you that 6 months later 100% of all your projects will fail. Low cost code monkeys and no productive end-results.

If you ever wonder how to lose all your friends, this is how to do it. You just became a worthless spammer.

Back on those days we developed company software. Databases were unknown to us, so we had to do everything with files. Oner trick to speed up searching for information was to split up data into 26 different files. Each one for a starting character you wanted to store and search back. Mostly the first letter of the last name.

Those files were text files so in case there was a software bug we could easily correct them by hand.

I am really getting old! I used to type in these BASIC games from that book! Then you power it off and the game was gone.

AGILE: "The art of self deception that you are fast and productive."

I challenge them to take one good developer and does the exact same thing. Less bugs, more clean code, easily deployable, elegant in design needs less documentation and intuitive to the user.

"By combining up front analysis and design of application architectures with rapid feedback on defects during short, iterative coding sprints, hybrid methods produce higher structural quality than Agile or Waterfall methods alone," according to CAST.

Yep AGILE creates crappy code. I told you so.

I thing people are getting confused:

• Writing good code: Your focus is on perfect code but your application will ergonomically suck and be a disaster to use. Look at Sharepoint, Sales Force, SAP.
• Writing the right code: Your focus is to develop your code for the product you want to develop. Your main focus is to give the user the best user experience, the best work flow, but your code will deviate from coding and patterns. Your code must deviate from best practices and patterns because it must be optimized for the project you need to create. Oddly enough this always results i a very compact elegant code that is incredibly easy to read and modify.

I never use that. In that I agree!

No OOP is actually your best friend, but when you abuse OOP and use it as some none-OOP namespace then you crash and burn.

It comes with free user stories too I bet /s

What's the point to develop for OpenGL when you add a layer that not only slows you down but prevents you from understanding how OpenGL can be used optimally.

When you develop for OpenGL, then your sole intention is speed and performance. You don't want a big huge anchor that slows you down in developing code and performance.

You lucky guy you can still do productive stuff. 90% of my time is absorbed by useless SCRUM stuff but work at 120%.

How about drawing a ladder with a pencil? I just realized that the question did not state that I have to program it into code.

I think we can also do a Phyton script that executes a Google image search on ladders and display that result.

WriteLn("H");
WriteLn("H");
WriteLn("H");
WriteLn("H");
output:
H
H
H
H

Also when you read into such articles, usually it gets away from the merit of whiteboard questions to "I promise I can do good work even though I can't satisfactorily answer your interview questions."

But I will fail the white board because my mind is wired to solve real stuff not stupid silly Fibonacci Numbers.

But here is the thing, you ask me the question and give me the time and Internet. I will come back an give you not only different variations of what you asked, I will probably also create a new one you never seen before that is even better.

The answer is yes if you want to keep learning 365/8/24 for the rest of your life.

Very nice wording!

70 year old? He probably invented programming!

No, I work with many older guys in their forties even fifties.

SCRUM master

Wooo, that may explain it. You have been brainwashed into developing a bad coding habit that will end up with 100% failed projects.

You paid a lot of money to snakes oil sellers: "Do these steps and you will become the best developer of the world". Sad reality is that you have been trained in quackery and bad coding habits. And you will never be able to unclear these bad coding habits. You became a code monkey, lost any creativity to bring software projects home and successfully.

Interestingly enough everybody is now following for SCRUM master and it does not add anything of value to your resume now. You are just a cog like the other 1000 cogs in the wheel. As a developer you don't have unique qualities that the others does not have. There is no reason to hire you because they have choice of 1000 other developers that knows the exact same thing as you.

Now how do you get out of there? Kick the SCRUM methodology out, it only slows you down. Learn something others don't know. Take something that has a higher learning curve and challenges your creativity. Don't become the slave of frameworks, take control become the master of your own framework.

I had unique chances to work inside SCRUM teams and outside, work in enterprise environments and in small companies. SCRUM cripples my productivity to about 10%. Enterprise environment between 30-50% depending on the team leader. Small company I work 120% productivity.

I have seen a lot of "Hello World" programs. The problem is not in the small scale programs that are below 1000 lines of code the problem is the projects that takes years to build and start at 10,000 lines of code and bigger.

You can use Nim for quick and dirty projects but the time you invest in that Nim project could have been used to create a C++ framework from day 1. There is a big different if you generate C code or if you write C code. If you generate C code it gets ugly pretty fast.

So we have another YACC (Yet another Compiler Compiler).

I have been playing with these way way back and for small projects they appear OK but as your projects scale, it is holding you back. In the end they make developers easy and sloppy and will create applications that look like Frankenstein.

If you want to have a useful degree go for electronics. Great for science because now you can create your own sensor network using ESP-12 modules to create sensor networks.

Even though I don't like IoT because there is no reason why my fridge should be connected to the Internet, you can create local networks (using a second wifi router that is disconnected from the Internet).

Real programmers don't do degrees. They say "fuck you" take a book a PC and learn it all by themselves.

Programming can't be taught, you either have it or you don't. 9 out of the 10 developers that are now out there are just mindless code monkeys. That is why modern software has deteriorated so badly.

From that blog post

It’s well known that creative people lose their creativity if asked to explain themselves while they are working. It’s the same with software. Programmers often have to work in an environment of one-sided transparency. These Agile systems, so often misapplied, demand that they provide humiliating visibility into their time and work, despite a lack of reciprocity. Instead of working on actual, long-term projects that a person could get excited about, they’re relegated to working on atomized, feature-level “user stories” and often disallowed to work on improvements that can’t be related to short-term, immediate business needs (often delivered from on-high). This misguided but common variant of Agile eliminates the concept of ownership and treats programmers as interchangeable, commoditized components.

Scrum is the worst, with its silliness around two-week “iterations”. It induces needless anxiety about microfluctuations in one’s own productivity. There’s absolutely no evidence that any of this snake oil actually makes things get done quicker or better in the long run. It just makes people nervous. There are many in business who think that this is a good thing because they’ll “work faster”. I’ve been in software for ten years, as a manager and a worker bee. It isn’t true.

SCRUM is the destroyer of teams and the destroyer of projects. Once in a while one team succeeds but it is not because of the SCRUM but because the developers in that team use pure willpower against the SCRUM that does anything to sabotage them. Without the SCRUM anchor these developer would probably produce 4-5 times more quality because they are not held back.

Successful developers don't suddenly pops up a magical solution out of their hats. They solve things quickly because years ahead that have been experimenting with solutions that in the future will be needed. They are already ahead of the curve and anytime they have a free moment the develop tools that come handy when a crisis occurs.

SCRUM prevents these good developers to think ahead and create solutions before they are needed. So this SCRUM is a temporary speedup until the developers en counter a new issue that they did not have a solution before. Your project dies now because you wrongly assume that your developers are bad.

You are one of the luckiest persons I know then.

It is literally a mechanism to turn developers into brainless code monkeys.

That one developer probably outperforms your complete team.

Why do people always assume that it is either waterfall or AGILE? Creativity of good developers that search for solutions can't be constraint into a fixed thought framework.. If you do that then you kill any chance of your project of success.

That is no developer!

Pair programming that is another thing! Back in 2000 they also talked about pair programming. I tried it and it fails. It always makes the guy that is less developed feel dumb and ends up in depression. It causes stress in these developers which is a shame because some of them are very good at what they are doing, just less experienced.

The main goal of continuous integration is to identify the problems that may occur during the development process earlier and more easily.

No it is not. It causes more problems and wasts developers time on stupid unit tests.

The reason is very simple, you create lazy developers that just do something until the code gets green again. And worse of all it makes your projects suck in the end. You have code rot and you don't realize until the project is dead.

Continuous integration explodes the number of developers it need to develop and with more developers you need team leaders and then managers for these team leaders.... Then expensive build servers then expensive automated unit tests.

I see the results of these Continuous integrations all the times. The green status LED means absolute nothing. Under that green LED status you have design flaws that no one questions. You are creating a project that is destined to fail because no one questions if that code is doing what it is supposed to do.