IoT devices, and projects with micro-controllers need C++. IoT and robotics is taking off so maybe it is good to learn the technology.

“I’m skeptical of AI on security,” said Ronald Rivest, MIT Institute professor and the ‘R’ in RSA. “Where we are seeing it becoming a wedge issue with the recent election is with AI bots in chat rooms. In 10 or 15 years you’ll be competing to find a real human in a sea of chat bots.”

I long back to the classical HTML pages that did not have client side javascript. All these fancy web sites have turned web sites in incredibly annoying flashy and always distracting sites that suck big on ergonomics. Not to mention they suck on any device.

On top of that they also generate tons of additional network traffic becoming incredibly slow. And on my older smart phone it crashes the phone because it is running out of memory.

One example

All of these assumptions are wrong

There are always 24 hours in a day.
Months have either 30 or 31 days.
Years have 365 days.
February is always 28 days long.
Any 24-hour period will always begin and end in the same day (or week, or month).
A week always begins and ends in the same month.
A week (or a month) always begins and ends in the same year.
The machine that a program runs on will always be in the GMT time zone.
Ok, that’s not true. But at least the time zone in which a program has to run will never change.
Well, surely there will never be a change to the time zone in which a program hast to run in production.
The system clock will always be set to the correct local time.
The system clock will always be set to a time that is not wildly different from the correct local time.
If the system clock is incorrect, it will at least always be off by a consistent number of seconds.
The server clock and the client clock will always be set to the same time.
The server clock and the client clock will always be set to around the same time.
Ok, but the time on the server clock and time on the client clock would never be different by a matter of decades.
If the server clock and the client clock are not in synch, they will at least always be out of synch by a consistent number of seconds.
The server clock and the client clock will use the same time zone.
The system clock will never be set to a time that is in the distant past or the far future.
Time has no beginning and no end.
One minute on the system clock has exactly the same duration as one minute on any other clock
Ok, but the duration of one minute on the system clock will be pretty close to the duration of one minute on most other clocks.
Fine, but the duration of one minute on the system clock would never be more than an hour.
You can’t be serious.
The smallest unit of time is one second.
Ok, one millisecond.
It will never be necessary to set the system time to any value other than the correct local time.
Ok, testing might require setting the system time to a value other than the correct local time but it will never be necessary to do so in production.
Time stamps will always be specified in a commonly-understood format like 1339972628 or 133997262837.
Time stamps will always be specified in the same format.
Time stamps will always have the same level of precision.
A time stamp of sufficient precision can safely be considered unique.
A timestamp represents the time that an event actually occurred.
Human-readable dates can be specified in universally understood formats such as 05/07/11.

Once in a while requiters have a random chance of luck but most of the time they have no clue what talent is.

Get a Prusa, it is worth the price, but they have a hard time to fulfill the orders, too many people want one.

The components you buy is almost the exact same price as you would order yourself. It also challenges your engineering skills since putting it together is actually harder than expected. I had a hard time to get the wiring correct and the end switches to operate correctly (Wires that got caught by some part of the printer and preventing the end switch to get triggered.)

It is very rewarding to have a real 3D printer up your desk that you can proudly show to family and friends.

The assembling took me 12 hours! The booklet did not explain enough for beginning engineers as I was. But that is the challenge. And it also makes you think outside the box, and you will be able to modify it and upgrade it yourself.

Prusa is a good investment, just don't use the cooling fan to cool down the plastic model using ABS. It warps too much and it also cools the extruder too much getting it a hard for the power supply to give enough power for the heat bed and keep extruder nozzle at 255 degree Celsius.

Expect these to be used to shut down WiFi security cams.

It sounds like the scrum team might be the problem.

SCRUM is the problem, it cripples my functionality to a standstill. Been decades in development and I can do the same job without even sweating of 4 team members and with a 100% project success rate.

but renaming and extracting functions out of huge blobs of code should be fair game,

Try that inside a SCRUM team with fixed daily deadlines! They will smack you in the face when you yet again renamed something and they don't recognize the code anymore.

We are in n a SCRUM team now, refactoring code is a big NONO nowadays because you have to hit your daily target at any cost even with bad code.

And why would you bother to create good code? The next idiot developer in your SCRUM team will damage it beyond recognition.

I see a lot of PR buzztalk.

As a developer I just want a good set of requirements, a decent process (agile, etc), and ample time.

That is not the hallmark of a "creative" developer.

"Writing code is a creative endeavor, and not a lot of companies fully understand that," said Lawson in an interview with The Register. "A lot of people think of developers as math nerds who want sit in a corner, eat Doritos, and be told what to build."

It was what the SCRUM teacher told us. Once you are in the sprint you have to create all the tasks. Even though you discover an issue that can be resolved in a next sprint task. He told us that we must accept reality that we will create something we don't like and that it will be thrown away later in the next sprint. We have to create that bad code to reach our tasks to be demoed.

Many developers got nervous about that. You are asking them to waste time and energy on something that is completely useless. This causes stress in the team.

At anytime when you're programming and thinking about using recursion, there is a 90% chance you're doing something wrong.

Spot on! I have created millions of lines of code and rarely needed recursion.

You and the business make the decision that you will hack a theme into the product in two days. It’s going to be messy, it’s going to be ugly, but you can’t afford to lose a huge customer just because your CSS isn’t quite right, right now. This is technical debt.

Yep that is how SCRUM creates the worst possible code ever known to human history.

As one SCRUM teacher told us, you will have to accept the fact that bad code will be created that will be thrown away later. You literally turn your development team into developers that don't care about developing code anymore. Why would I create good code when it is gong to be thrown away anyway?

Extreme programming always fails

• Too many rules.
• Good developers are not social.
• If you put 2 developers behind one PC they will speed up but the nerd ego race it causes to refuse to be the beta guy will race them into a burn out.
• The guy that is behind the keyboard is always the dumbass. He is a dumbass because he has to use his brain to type the commands while the one behind you has all his brainpower be multiple steps ahead.
• Very depressing over time to be the less experienced developer because the experienced developer will always out-win you. If you want to have a depressed developer that will jump of the highest building, then force him to do pair programming.
• Complete waste of development time, you slow down experienced developers to the level of the lowest developer. Some things you simply can't explain to other developers because they lack the background and experience you have and will constantly have the feeling that you are wrong.

Agile, scrum, pair programming, it is all quackery tools that will only make your projects fail and your team depressed.

Red gate became incredibly expensive and the tools are not worth that kind of money.

Sometimes creating your own custom tools are even more efficient.

The biggest dangers of automated code testing is:

• Sloppy programming, the developer will commit just something and if it turns green then he can go home. If it fails then he randomly changes something until it gets green.
• Loss in productivity. You are more busy making the test turn up green than actually invest energy in creating stable code.
• Tests that are simple wrong to begin with. You build your code around a test that is faulty.
• Unnoticed design flaws that will cost you dearly because you relied on the green status for so long that you never wondered to question if that code is actually good.

It seems impressive until you realize that it is only useful on a very simple hello world like application.

I have seen again and again yet another vendor trying to sell a magical unit testing tool that will resolve all problems. But in the end they work great for certain nice cases and are very expensive to buy. On top of that they add additional layers of complexity risking to fail to detect other design flaws.

It is tempting to use these tools as a quick win but when you rely on these tools too much you can end up with a project that is doomed from day one.

The problem is not the code reviews but the timing in code reviews that are enforced into a SCRUM sprint. The inexperienced will be daily bashed by more experienced developers over and over again until they drop out with a burn out or leave the company.

There is also a risk, that developer start to create sloppy code knowing that the next guy will catch them. The problem here is that the next guy may be worse developer than you and assume that it will be all right. The same for unit tests, relying too much on green lights may actually reduce the quality of the code. It is tempting that to stop analyzing why the code is read, they just add a quick hack that it is green again and they hope that the next guy will solve it.

The none-social NERDS tend to produce better code but the bad social pseudo NERD will become best friend with the SCRUM master an they will tend to offload the hard work onto the none-social NERD. Over time they will start to make the none-social NERD for all the mistakes that are made to the bigger bosses.

You might assume that IT managers would grasp this logic, but sadly many of them don't,

Managers pretend that they understand what they are doing. It is their little helpers that does the real things. Also mangers will not admit to other managers that they have no clue what these hype words even mean. They will clap and cheer to the power-point presentation about AGILE as the next best thing like sliced bread.

The success or failure to these managers is how much they slow down their little helpers.

Observe how they start to panic when these methodologies disrupts the happiness of their little helpers and they start to fight each other because projects starts to fail.

This is VERY interesting.

Marketing BS.

Don't pick one, pick 2 or 3 (at least one c/c++) and learn them together. the days that you developed only on one language have long be one. Nowadays it is the ability to pick up a new language and master it in 1-2 months. You don't have to completely understand every part of it, just enough to develop your project and you learn as you go.

The key to learn all this is to make your mind plastic for new languages and technologies. When you can do that then you can last decades as a developer.

C or C++ are just 2 different variations of the same when you develop. I always go for the C++ side when I develop fast code because it is easier to develop. intellisense helps me better.

Of course I say F$ck you to design patterns when I make C++ OOP, shine.

One of the tricks is to copy the "this/self" variable to a local variable and use the rest of your code withing that method with that local copied version.

Why does TIOBE think C is declining? “Some months ago we already listed some possible reasons: it is not a language that you think of while writing programs for popular fields such as mobile apps or websites, it is not evolving that much and there is no big company promoting the language,” its note added.

That is rubbish. C didn't sink, it is these mass imported low wage 3rd world developers that had a 3 month course in some Web/Python and is now flooding the market ending in the worst possible designs and coded ever recorded in the history of mankind.

C is very well alive in development projects that requires an IQ level above 100.

There is a massive extinction coming soon when all these hype projects fail and only people that have the capacity of understanding C will be hired. yes the people that develop robots.

Been in several ones of these of the last years. All projects fail and the teams feels miserable.

• We are NERDS. Nerds aren't social, and aren't team players.
• We are NERDS, Nerds want to do something useful not wasting precious time on useless meetings.
• We are NERDS, Nerds always work at 150% of our capacity because it is fun. Agile methodology cripples our functionality and drops below 10% capacity.
• We are NERDS, Nerds have fun in being agile, but the Agile methodology forces the Nerds into code monkeys and kills all the fun.

Also NERDS are smart people and are very aware that you give them a false sense of choice. I can guarantee you that your best NERDS already are surfing the Internet searching for a better job away from Agile.

Just start somewhere, you will make tons of mistakes but that is how you learn. Just don't let big ego-ed bullies put you down, their big ego is to compensate their lack of development skills.

Take something and make it better. You don't have to create something from scratch.

Agile never fixed the mistrust between stakeholder and developer, it just tied the developer's hands. Terms like "polish the cannonball" are used to beat down and suppress the desire to do things beautifully and just turn software development into a machine in and of itself.

Nice wording, but it is exactly that.

You just described how I do it :-)

Programming IS hard. Programming that is user friendly and actually is useful and you finalize it to the end with no bugs.

I work with several female coders and I disagree.

Typical responses I hear from developers are:

• I can't reproduce the error, so it does not exists.
• You have tested it wrong, first you must click button A and then B not B and then A.
• My program crashes because you did not install service pack 34.54.3.45
• My program crashes because that printer has the wrong firmware v578.651.26.21
• My software crashes because you installed it on a D drive instead of a C drive
• My software crashes because you added a space at the of your name.

When you as a developer already take into account how users make mistakes or even when the computer you install on will not be perfectly configured, you will be less on phone support and more time to develop new cool features.

The same for the code, if the code mimics how the user uses it then it is almost a one on one to test your code. I do not have enough time to explain this.

the denial of problems and blaming the user.

I have seen this in any language. It is extremely rare to encounter a developer that cares about his code and especially designs it in such a way that it makes the users happy. In a lot of cases, designing, the code for the user actually reduces the complexity.

I know many developers that are 40+.

Ignore that troll, your information is worthwhile.

Don't limit yourself to web development. Everything you now learn will become obsolete in 3 years. Web development may be a dieing art from 3 years from now.

Again, it really all depends on where you're working and how closely the organization decides to adhere to true Agile principles. From what I've seen, it probably won't last forever at most places simply because there is so much downtime associated with it.

You bring me hope. :-)

Software estimation does not work, it never worked and it will never work.

And the reason that I cannot be predicted is because you are doing something that has never been done before and will never be done again.

The big issue that I have with frameworks is that software ergonomics has gone down the drain in the last few years. Something that I could do with 2 key-presses now requires me to move the mouse 20 times, scroll 5 times down and then move the mouse pointer to the other side of the screen to go back.

And it even got way way more worse for disabled people.

But this is not a good thing, all these animations all end up becoming the most irritating and ergonomics worst web sites ever known to existence. They are all mimicking the irritating advertisement that screams for your attention and distracts you from the real content.

Jesus, rules rules rules, you are worse that Reddit.

And yes this is related to programming. Git is a vital part of modern programming.

When you put all your code sources on-line, you have no way to know if someone is slightly modifying it behind your back. And don't tell me that Git is this magical thing that no one can modify behind your back. Anything that is "digital" can and will be broken.

Github Nukes Repository Over Use Of The Word 'Retard' https://www.techdirt.com/articles/20150802/20330431831/github-nukes-repository-over-use-word-retard.shtml

When you look at Windows 10, regular updates but still I have no clue what on earth changed except for some icon changes and font changes.

Windows 10 from 1.5 years ago looks and feels exactly like now. Except for the many DRM breakages of my licensed software and regular blue screens.

Sometimes the wheel cannot be recognized as wheel anymore.

I understand why he is doing this but in the end it is not going to be helpful. Quit the opposite.

The problems you will get is:

• Yet another framework to learn, that takes away resourced, and CPU cycles.
• Someone has to keep it up to date all the time
• You will add stuff to your app that only make the app more complex. You add stuff that the app did not need in the first place
• The biggest issue: If everyone can do it that, you will end up an explosion of thousands of badly developed apps poisoning the well and make people lose interest in apps because they all suck.

If the code is used for unethical things, it will eventually destroy the company that spec'd the code.

It will probably kill you if that code is used in a hospital device and you need surgery.

And your code may also be used in that processing plant that processes toxic waste at 10 km from your home.

Good OOP design scan be easily recognized: The usage of the code becomes elegant and easy to use.

The reasons why 90% of software developers can't develop good OOP is because they use it as some glorified namespace. A complete wrong way of developing good OOP code.

If you are a developer you learn anything. But since you have limited time and resources you focus on what is on the surface only, don't waste your time on online courses just a waste of money and time.

This guy is spot on. Good developers have this ability to learn new stuff and come up with elegant solutions. But when you ask them a question then their initial response will be "dunno", then the day later they have learned anything about this topic and become the expert.

You don't need to be good in algebra to become a good developer in enterprise and web software. It basically resolves to +, -, * , Trunc() and Round().

In real world applications, it is not that important.

The small f after 2.5 in float declaration is required to denote float value in C#. If we omit the small f , the value 2.5 becomes double precision.

float: 1.5 × 10-45 to 3.4 × 1038 (32-bit number)

double: 5.0 × 10-324 to 1.7 × 10308 (64-bit number)

float num1 = 2.5;  // 2.5 = double precision so it will be down-converted to float

This will work too but when you work with floating point values any conversion could end up with loss of accuracy.

num1 could end up with 2.50000001... or 2.4999999...

float num1 = 2.5f;  // 2.5f = already float precision so no down-conversion needed

This will guarantee that num1 will be 2.50000000 to start with.

Edit: I just checked

float num1 = 2.5; // Compiler error
float num1 = (float)2.5; // Compiles
float num1 = 2.5f // Compiles

SPAM!

It would be less joyful when everyone only upvoted. There would be no challenge and I see in your code you love a challenge.

Finally a link to a page that actually does learn you about programming instead of these eLearnig Spammy links that are utterly worthless.

JSON is the de facto standard when it comes to (un)serialising and exchanging data in web and mobile programming. But how well do you really know JSON? We'll read the specifications and write test cases together. We'll test common JSON libraries against our test cases. I'll show that JSON is not the easy, idealised format as many do believe. Indeed, I did not find two libraries that exhibit the very same behaviour. Moreover, I found that edge cases and maliciously crafted payloads can cause bugs, crashes and denial of services, mainly because JSON libraries rely on specifications that have evolved over time and that let many details loosely specified or not specified at all.

This is what I observe, the web team is none-stop busy keeping up with the framework changes. They have to, in order to keep the software running. It is a rat race. And the issue is that they use up all their time and resources to keep it running and never manages to learn software development in depths. They never get fully experienced in creating complex projects they only stay at the surface level.

All the time. The age of the script kiddies that loves frameworks and have never learned to think at deeper levels. That is why I warn people to stay away from frameworks so they get forced to think further than easy quick solutions.

I started in a 3 man company and I now work in a giant corporate for years now.

A team of Indian programmers could do my job for what I make, it'd probably cost the company millions after they corrupt a database, but they could do it.

I don't think any noob developer should be able to cripple a database when they touch a line. That would be bad design.

A simple corporate crud form doesn't need to innovate everything.

I think you lost your imagination and have forgotten how great software can be written. Everything looks like a nail if you only have a hammer.

I bet that every time you get a new project the first thing you do is clone your project, rename it, change font and there is your new project. I am sorry an Indian freshman ath half your price just from school can also create a CRUD project.

We ended up here because of the script kiddies wanting to continue on with the jQuery, Angular, Bootstrap, etc. game where everything is sad and similar instead of making something new and bad ass.

Everything is cloned from the other 10 competitors. It is yet another FB clone just with different font and back color.

However, learning to use a framework or two is not a bad idea. Bottom line: People need jobs. Even if you are a "script kiddy" who gets replaced after a year or two, you still got a couple years of employment out of it.

I do agree with this. Staying away from it does not mean that you are not allowed to use one to see how it works and pass a HR exam. But too many times I have seen that the framework causes more problems than they solve.

I really wish that people don't create web sites that have these giant fonts and hurts my eyes when seen on a desktop. You give up after paragraph 2 and off to some other site.

We live in 2016 for gods sake. There is no excuse to not write code in such a way that it it looks great on a tablet and on a desktop.

How hard can it be to?:

If Desktop then use Desktop_CCS 
else use Tablet_CCS.

If anybody should be worried about their skills losing value then it is the programmers who change their tools and technologies constantly. They do it so quickly and often that they gain no significant depth in their knowledge.

This is so true. As a developer you don't become better, you stay at script-kiddy level. And there are 100 of other script-kiddy level developers that wants to take your job.

The development experience is indeed worthless over time, however developers that have decades of experiences are very important for your company. The fact that they are still doing this job means that they are the top of their field through natural selection. The bad developers all became some kind of manager and lost the ability to develop.

These older developers might not use the latest and shiniest technology. Not because they can't follow or don't understand, but their experience is grown enough to know what works and what will fail.