Found the journalist.

Tea? Are you a journalist?

You don't need to be smart for coding, just the willpower to nail that solution and become better than the average.

Most modern day programmers really suck at programming. They are so hyped up in design patterns that they have no clue that they really suck at programming. Also stay way from this SCRUM madness. Follow this and you will end up with the most fucked up program ever recorded in human history. The world needs good developers that have a very creative mindset, can create technology out of thin air, to nail the ergonomic design.

This world has lost the ability to reinvent the wheel, the current wheel developers are reusing has become complete rubbish. Big giant monoliths pretending to be small nuget packages. Nowadays you can't even create a "Hello world" program without sucking own 12.154 dependencies.

Teamwork, good projects suck when teamwork is involved. When teamwork is involved your project becomes the worst developer in the team. All you end up is with a team of lazy developers.

Best teams do not work as team. Best developers are competitive, they don't teach each others ways; best developers look at what the others have done and absorb what is better and reject what is worse. I become better than my team members because I want to be better. The other team members are now forced to up their skills to become better than me. In the end your complete team becomes way better than other teams because now you develop according to your best programmers. And you keep on staying in this team because they are worthy my level because they challenge me to become even better.

My key is, follow the masses in development and you become obsolete in a few years. Don't follow the masses and you will outperform all these other developers that will burn out and everyone will want you.

There is no answer in this, just jump into something and try to get as wide as possible range. In software there is never a predictable way to know what is needed. There is never a predictable way to know what you have to learn for the next job.

The key is to start with something, and as you find typical jobs you then tend to focus on the skills to pass the job interview.

.NET core is not lightweight at all! Load one component and it sucks down 10.000 other components to let that one run!

The other issue I have is that every single day there is yet another update. You never have a stable version!

That is not how programming works.

1000 of typing monkeys does not create a good book. Neither will 1000 scrum developers create one useful product.

The annoying thing about AI is that you have to teach what you want. So instead of programming you have to train it by telling what it should do. Imagine guiding 1000 typing monkeys to write a good book, they won't listen to you.

The other issue with AI is that AI can only create what it learned to create. It becomes an less than average developer creating sub standard solutions.

Out in the real world with the #learntocode madness and scrum we have 100 out of 1 developers that are pure crap. Good developers gets outnumbers by 100 bad developers that undo their programming. Interesting is when a company is downsizing and fires most developer, the good developers suddenly becomes productive again.

AI assisting developers to create good programs faster is another ballgame. A good developer can focus on what he wants to build and the AI is a glorified spell checker.

AI does not benefit in generating programs. We already have thousands of skins available for code that are exactly clones of each other. There is nothing new the AI can create it already exists.

But a good developer can out of the blue invent new technology to create things that does not yet exist optimized for your company. Good programmers can escape the box of limitations and create something new. I call it cheating because they bypass coding rules.

In addition when AI is thought wrong, it gets harder to get it back on track.

And yes I have been learning everything about AI the last 3 years to have a feeling what it is able to do.
It is still really disappointing, and takes good developers to guide it to become somehow practical.

You want to become a leader by having cloned software that look identically like the other 100 direct competitors? Why would a customer choose you over the 99 other companies?

The only thing an AI will be able to do is slight variations of what already exists. If you want to be successful as a business then you must be a leader, not another clone of the competition

Won't happen. When you look at tensor flow, it is still programming. Also the Ai to replace a human is way too costly to maintain and sucks so much energy that on itself causes climate change.

It does not matter where you start. Programmers are self-learning, no paid course will make you a good programmer. Just get a compiler and start making your hands dirty. Any compiler is good, any language is good, just do it.

That is why you don't realize how inefficient scrum really is.

I give you a clue, SCRUM:

• Feature1: dig a trench, put a cable in, close the trench. (5 user stories)
• Feature2; dig a trench, put a cable in, close the trench. (5 user stories)
• Feature3; dig a trench, put a cable in, close the trench. (5 user stories)
• Feature4; dig a trench, put a cable in, close the trench. (5 user stories)

End result = 5+5+5+5=20 user stories

None scrum:

• Dig a trench, put cable 1,2,3,4 in and close the trench. (8 user stories)

End result: 8 user stories

Well anyway, we are now back on track with 0% stress and 100% productivity. Things gets done now.

End result, 4 times SCRUM in different companies in the last 10 years: 4 out of 4 FAIL!

On the contrary we are following scrum by the book. Everybody had to follow scrum courses. We had even a personal scrum coach for a very long period. The funny thing is that when he took over to show us how it was done he failed miserably. Hahah

The proof is in the pudding, projects that becomes successful and our team is now producing projects that rocks. And we just started to accelerate. The other scrum teams can't keep track with us :-)

QA and UAT is still there, nothing gets pushed into production untested by other teams. Don't worry.

Without scrum, when we discover issues, or even finds new bugs in the code we can fix them instantly without having to go through an enormous waste of time through the sprints. With scrum we were forced to put a feature to done even buggy. Without scrum we put a feature done when it is ready and the quality is met.

On the contrary we are on a very efficient team only held to a crawling halt by the scrum methodology.

That 15 minute standup meeting is not scrum, that is only 1% of scrum.

And after 2 years all those in favor of scrum have left the projects. We finally have now the time to fix the crap and make it function in record time. Those user stories that is inefficient crap. Three weeks of sprint, and no way to respond fast and fix the thing that took ages. Without the scrum, ask us anything and within half a day or 2 days it is in. That is agile development, not that slow paced scrum sprint.

In the next weeks the very efficient functioning of our team that are now free from scrum will create shock-waves. More production, less bugs, faster development, better improvements, performant code. That is what you get when you use your developers at their peak capacity instead of this crappy use story related that cripples your developers and make them feel unhappy.

We are not restricted to the project manager anymore, we are faster than any project manager.

The last 3 years software has been at a stand still, nothing new is created only icons, fonts and flashy background changes. Modern day software are ergonomic disasters.

That is not how software works. scrum is the most inefficient system I have ever met. It prevents your good developers function as efficient as they can and having to lower their standard to your worst developer in your team.

Two years I worked in a team where you need 10 people to do exactly the same thing as one developer that does not use scrum. Thanks god they finally realized that it sucked and now we are back in the none-scrum mode and projects suddenly flourish without stress.

Scrum only benefits bad programmers into thinking that they are good. Scrum is like paint by numbers and then think that you created a Michelangelo.

But they never do what you need. The code around it to wrap it and the dependencies its needs is only a short term gain but over the years one pain in the ass to keep functioning.

I get hired to fix broken projects than complete teams's canno't make stable over years and did their best to have the best data structures, and algorithms and libraries.

That is the issue not everybody has the brainpower for this. Different people are wired differently.

I actually never seen code that follows good design principles, data structures and algorithms work in real world situations.

They only work in new prototype projects from scratch but scale very badly. These ideas are built on hypothetical perfect worlds, never real world situations.

You are so right in this!

They will burn out faster than you can say "Ja’loja"

The annoying thing with coding is that it is a 365.2422/7/24 none stop effort. You eat behind the PC, you drink behind the PC you even take your laptop to the toilet. Blink and a 18 year old replaces your job because he is ahead of you.

The other thing is that 18 year old that just replaced you will be replaced 6 months or 1 year from now because he too becomes obsolete. So the world is creating one giant pile of throwaway developers that will end up in a burn out state and jump from a building.

Now the good news: Those developers that are on top of the food-chain and evolved while other developers gave up or jumped from a building will be the ones that companies need after they burned through the complete population. Those will become the new millionaires.

AGILE sucks!

You are referring to the framework, I refer to the C# generated code itself versus developing an C++ application.

An why is everybody assuming that web is the only possible thing you can create? There is more in life than web development.

There are no best ones. However all those that went the CoC way are to be avoided.

I am not going to waste time on these CoC communities. As I said, Code comes first for me. I am not contribute code to a team that does not have a winners mentality.

None, Code first! Irrelevant of the tools, languages, tools,....

All developer that came out of school the last 5 years and learned to program are fucked up. They have been brainwashed "how to think" and create crappy projects, they never learned to think for themselves and invent new ways to nail down your project.

The sad reality is that they are not even aware how badly they suck. The proof will be in the pudding because 5 years down the road they will lose their job as a developer because they are still stuck to the ways they were brainwashed. It is almost impossible to unlearn your bad behavior in software.

Modern developers have lost the ability to think in multiple dimensions. All they have learned is paint by numbers and one dimensional thinking.

Most projects that use flashy design are hiding the fact that their projects sucks.

The impressive lines you see are just error messages telling her that she is doing it wrong.

I am not a java expert

• Verify how getFaceValue(); is implemented. I am wondering if you return an int in here or are casting an object to an int value in this part: "int x = die1.getFaceValue();"
• There are 6 different "int x, y, z" that have the same name.
• You probably used copy&paste. I checked if you did not have typo's. Java works JIT I assume could an invisible character break the logic?

.NET C# is the next best thing to C++. It is a very powerful all round language that scales incredibly well and also is very performant. Been programming it since 2001 if I recall. Also it is a fast compiler and you get results fast.

AGILE:

• Open the road, put a cable in it, close the road.
• Open the road, put a cable in it, close the road.
• Open the road, put a cable in it, close the road.

Super AGILE:

• Look at what the company needs and is going to need in the future. The Open the road, put in cables 1,2,3 plus 2 cables to be used in the future, close the road.

AGILE:

• Open the road, put a cable in it, damage the other cable, close the road. Log a bug for next sprint

Super AGILE:

• Open the road, put in cable 1, 2, 3, fix the broken cable A, close the road.

AGILE:

• Open the road, lose focus because of the stand up meeting, lose an hour to discover that the commits of the developers broke your previous commit, debate 2 hours, close the road.

Super AGILE:

• You work alone, no other idiot broke your code, no meetings to lose your focus, you plan ahead and prepare your code for fast changes, you take in the toughest job when you feel 150% capacity and you do boring jobs after a night out with the friends. You have higher quality of code because you realize that no one of the other developers will fix your bug so it will get thrown back in your face next time.

90% of the so called AGILE is bureaucracy and holding you back to develop fast as an experienced developer that can tackle multiple projects at the same time.

You can easily verify my claim, take a developer that started in the 1990's and did not yet get brainwashed with this AGILE madness. Ask him to do the same thing as your complete SCRUM group would. In 2-3 sprints he will bypass your complete team because he does not get the management overhead of the SCRUM team.

Real programmers can program in any language you throw at them. They never say: I refuse, they always say: When do you want it?

Welcome to my world, I have been doing this for years now. But it made me stronger, I became a fast developer ultra agile that can beat a scrum team. If they don't restrict me.

We nowadays have a complete generation of developers that have no clue what good code is. They grew up with buggy, unresponsive code so they. think that this is normal. They are completely unaware that it can be done, very stable, ultra fast, zero bugs and deploy within an hour.

I keep on telling them that if they want it, I can fix it. They look at you not even understanding a word what I have said. They think I brag but then I do it.

Why use Linux when you can get the full functionality in your hands?

Since there is no fun anymore to developer for SJW Linux, how about starting your own OS from scratch?

My brain. I used to use modelling software back around 1999 but they all failed to meet the need. Modelling tools and even these stupid "Design patterns" are a limit to your creativity to build great software.

Modern modelling tools are even worse nowadays than back on the old days.

You have to know that they claim that these "Designer patterns" and modelling tools are based on the best developers techniques. It is complete marketing BS because these "Design patterns" are only the crystallized creative end-result of the best developers. It is only a shadow of what makes these best developer good: Their creativity to invent new stuff out of scratch to solve the problem. By using these "design patterns" and "modelling tools" your brain gets frozen in a static way never to recover.

I want to see progress. I want change. I want state-of-the-art in software engineering to improve, not just stand still. I don’t want to reinvent the same stuff over and over, less performant and more bloated each time. I want something to believe in, a worthy end goal, a future better than what we have today, and I want a community of engineers who share that vision.

You are not alone, I am daily fighting the the goal to make programming great again.

I hate this SCRUM! I hate it because developers that like it becomes losers. People that used to be good developers became stuck in the losers mindset and nowadays they even don't bother to ship something that is good. It is frustrating to have a struggle to make good software because in their losers mindset they are pre-programmed that it can't be done. Their mindset is stuck to this silly believe that you need a complete SCRUM team to do the job of one good developer.

However not everything is doom and gloom. The best developers have already moved on to a world where there is a steeper learning curve: Building their own hardware from scratch. Design PCB's, solder the electronics, build their hardware, program their hardware, build their own hardware tools like 3D printers and laser cutters. The bad developers can't reach that level anymore.

I do think that kernel developers in Linux, now that Linux has turned full SJW with their stupid CoC, will find new ground away from these forced social PC. These kernel developers probably will start to create their own hardware.

I never understood why developers have this stupid need to work together to build a giant project together where complete idiots can destroy your code and you are called a bully. Working together means that you are a beta. real developers take charge and becomes the alpha.

Your comment does not computer. I have no idea what you are talking about.

Programmers come in all shapes, including stupid ones that do''t even realize that they suck in what they do.

C++

Experimenting for the sake of experimenting, should not be done.

I actually learned this multiple code paths exploration back then when I needed to develop software for massive amounts of data processing in as short of time with limited hardware. I created multiple different solutions and measured the speed. The most effective one got continued and the rest removed.

Doing this will temporary create a more complex solutions but the complexity will be cleaned up and in the end you will have a deceivingly simple and effective code. But it can be done only when one developer modifies this part, without interfering by others.

Nowadays, my aim is not for speed but in ways where testing becomes way simpler, and once deployed the user does not get blocked when a bug shows up. The code will become more complex but the log files will be more readable for none-developers.

I tried many times to come up with a good explanation, but I can't without giving too much details in my projects.

I see deterioration of many teams in my company because they choose the lazy ways and the business value only. It is only short term thinking quick and easy gain. The standards are getting lower and lower but they don't realize it and neither the managers. The reason is because they play it safe, small incremental changes too afraid to change something dramatic because the code sucks.

Why don't I develop because it has business value? Because that way I will explore new code paths and solutions that does not have immediate quick values.

Why will I not be lazy? Because I will go off the safe path to explore different paths and may find news solutions that are more compact in code, more elegant and way easier to deploy.

Why don't I work in pair? Because it always end up onto debate, debate debate and pointless discussions because the other developer lacks the coding skills to see what I am doing.

Yes

It’s very simple: if you can not do work and still gain the same value as you would doing it, then don’t do the work.

I don't like this sentence. That word "Value". This stupid word is used all over AGILE/SCRUM but cause more problems that it fixes. This very word "Value" as in "Business Value" is the primary cause why you now need 10 more people to do the exact same thing as developers could single handed 5 years ago.

Modern software developers are scared to change code, they keep on playing it all safe. Only small incremental changes are allowed otherwise it is a big no-no.

Don't get me wrong, I don't gable with the code or take any risks. I aim for maximum productive results with zero bugs.

It is time to abandon Python as a language. Once infected by SJW's there will be no stop in imposed changes to a point that no project in Python will function anymore.

Python, is dead now, best to move on to another language.

Patriarchy- wife

They could rename "Python" to "Vagina" since the "P" in Python clearly refers to Penis.

I never wrote my own compiler but I did write my own 32 bit OS. Does that count?

Angular: the attempt to to to run a web-page-server and the back-end server into your browser. nothing good can come to this. It also answers the question why modern sites suck and are also so unresponsive slow.

Nice

If you can’t quite manage that, I’d advise you to take on less work in each time period, until you’ve taken on a small enough batch that you can actually get it done.

Massive FAIL! This never works in good programming.

In good programming you look at all the possible issues and then create a multiple dimensional level solution that solves it elegantly. The code will be a little bit more complex but it probably collapse the number of code to 20% of what you would have created.

And if done correctly, this slightly more complex code will be self correcting and self testing where your need for mocking and unit testing will be reduced to the minimum.

Good developers don't write code, they write cathedrals where every part has a function and well thought place.

You need a soft deadline. deadlines are important because then we wrap everything up to a complete functional project.

What would be better is to have a soft deadline, and make developers try to do everything they can in this given deadline with certain directions to follow to. Any good developer will optimize the time and resources because they love to create and also love to win.

This blog post indeed is trying to create a new hype because their previous hype failed. It is the exact same people that tries to cover up their previous mistake by introducing yet another method that will fail exactly the same way.

More generally, developers’ work should adhere to the foundational principles....

Jesus, quit the "principles" reasoning!

The best developers don't follow principles, they create principles based on what they need. They don't follow patterns, they invent patterns for what they need. And what is needed depends on the company's needs.

Get rid of these SCRUM teams and you will notice that one good developer will replace one complete SCRUM team when they are allowed to do their work. Take developers that started their careers in the 90's. the period where good developers came into existence because they self-learned it all by themselves.

I’ve tried to help those people understand that their organization is doing “Agile” wrong: they’re not doing what the Manifesto authors recommended, what Scrum recommends, what the many Agile Software Development experts recommend.

WRONG! SCRUM sucks also Agile Software Development experts suck even, bigger!

Claiming that they are doing it all wrong, is a clear indication that you have no clue what programming is. The big giant flaw in by these co called Agile software developers is that they try to "quantify" software development and assume that software development is team work and can be teached.

• Great software is ready when it is ready, not when time is up.
• Great software cannot be planned and predicted before, you create a fuzzy goal and ask the developers to create something that does this.
• Great software developers work efficiently alone. They need to build their code reliably and that does not work when you get some idiot crippling all your code at random locations.

Now brace for impact, anyone that was brainwashed into SCRUM methodology, your life will suck because it is going to take many years to unlearn these bad behaviors. If you came from school and did not develop 5 years ago, then your brain was never trained to be creative and your career is over.

Shockingly, the engineering team still cares about the product and customers! In fact, their biggest complaint is that they aren’t allowed to fix bugs and make small improvements which will benefit the thousands of paying customers they already have.

That is exactly the reason why AGILE/SCRUM fails. The team gets prevented to create out good products and get demoralized. In the end no one cares anymore and look out for another company.

This rapid release of tools have given even most die hard's of latest technologies a burn out where I work. They used to be excited now they stopped caring. Maybe they started to realize that they are more busy updating to the latest tools and learn new stuff than being productive.

With C# I can develop software that comes as close as C++ but compiles in minutes while it took 30 minutes in C++.

I don't expect you to believe me but I did build number crunching software in C++ and C# where speed meant the difference over the competition. I only lost about 5% of the speed in C# over C++.

C# Has the perfect balance to create literally everything. Of course in the hands of a seasoned developer. (I started with C# and .NET 1.0) so I know my way around.

And I didn't start with J#, I started with Z80 assembler. That was my first contact with programming back in 1982. J# was the first time I got in contact on Java.

Microsoft is fragmenting their developers tools so much that it becomes so diluted that no one cares anymore. There is no point it going to TypeScript 3.0 if they are going to release the next TypeScrip in 1 month from now, then another one, and another one and another one.

Rule number one in successful projects: "Pick one and stay with it until it is completed."

Don't change your language, framework or tools midway your project because you create a setup that will fail!

I have 30+ none stop experience in developing software, I can keep up with the rapid changes. I can keep up even if those changes accelerates 10x. But my point is that other people can't. 95% of the developers that have met won't last 10 years, 50% probably won't survive 3 years.

There is a human massacre in the making of burned out people.

I started with J# back then but then jumped to C#. C# is still my favorite language but I keep my Java knowledge up to date.

The article is correct about the Ukrainians. I know some of them.

Western Europeans are degrading in quality. The reason is the SCRUM, we feel unchallenged and our jobs are as exciting as the script kiddies jobs. Two years down the road and we have not done anything productive, just meetings, meetings, demos and more meetings. But I keep my knowledge sharp by doing projects at home :-) Many already left for better places, I think by the end of the year the only people they will have left are N00Bs that just entered the programming field. Have mercy on their souls!

Your core programming principles can be learned in 1 or 2 hours. You can learn this at any moment when you need to. You keep on referring to simple "Hello world" applications. This is not what this you-tube clip is about.

But you don't have to believe me. Programming as a profession sucks the life out of you if you are not built for it.

It is only a short time burst, then you become obsolete. What is not visible at the developers side is that developers gets replaced by newer ones fresh from school that were not yet spoiled with technology that is 1 year old. You have done so much effort to learn to code and then after your 5 minutes of fame (about 1 year) no one wants you anymore.

I understand your reasoning but the hard reality of the coding world is completely different.

Your knowledge of writing an email and your boss to understand the email is obsolete in 3 years. The rate the technology is changing is every 3-4 weeks nowedays. If you don't follow a certification every 3 weeks then you get outperformed in maybe 9 weeks.

Currently there is a rat race to the bottom and we are burning up new developers at a fast pace. Those that manage to stay being a developer have evolved that way by keeping up to date 24/7/365 for decades.

It gets even worse, the code you learn nowadays will be stuck into your brain. In order to keep up to date you must have the capability to unlearn what you have learned before and relearn something new.

Most of the developers that enter the developers field will become burger flippers in a few years from now.

And it has an expiration date of only 3 years. Three years from now you won't' understand any code that is up-to-date because the language and notations has completely changed.

It is like losing your language ability because in 3 years from now they jumped from English then Chinese then Arabic then Spanish then Chiniglisch.... And modern days they mix languages and coding styles withing the same application.

If you don't have a natural tendency to figure it out all by yourself, then your career of being a developer ends after merely 3 years.

Good developers are not formed by educating them, good developers will automatically learn everything without ever being taught! All developers that does not have this natural instinct to self-teach and explore uncharted territories will be wiped from the work force in about 5 years.

Look at the speed they bring out changes in languages and technologies. Even the ones that were excited one year ago are now being burned up.

There is no difference between C and C++, just sugar syntax. under the hood, your object gets transmitted as it was the first argument.