|
Just some coming trends I've been getting hints of that some of you may not have become aware of.
1. NoOps. Let's face it, Agile is OK, Lean is a little better, but ultimate having absolutely zero 'friction' between the developer and the customer is where we need to get. NoOps addresses this issue by ultimately pushing the development process to the customer, who knows his requirements better than anyone. You take requirements from the customer, complicate them significantly using core NoOps processes, and send them back to the customer to implement.
2. C++ 21 is going to introduce the most powerful language feature yet:
main()
{
Program<Implementation>();
}
A 400GB template library of every possible program implementation will be part of the new standard template libraries. This is somewhat offset by the minimum 16 hour build time and minimum 20GB program size.
3. C# Darkode. Your company's code is the family jewels and if you lose control of that to hackers or competitor's espionage all of your work and investment will be for naught. The next version of C# will make your code immune to such problems by introducing so many syntactical options that no one can understand your code even if they have access to it. With a mazimum of 2.85% of your code being actually related to the problem solution, finding the important lines of code will be essentially computationally infeasible in medium to larger code bases.
4. Containertainers. Managing all of your containers and their options is now becoming a serious challenge to many companies. Containertainers are containers for your containers and their configuration operations, simplifying your container deployment and management process. Work is already under way on Containertainertainer technology, in anticipation of projected containertainer deployment growth.
5. PlausDen. In order to avoid potential legal and financial blow-back from software bugs, your company needs to develop solid plausible deniability strategies. The upcoming AllPacks package manager is a key aspect of PlausDen planning, insuring that you never actually understand more than 1% of the code that you deploy, and hence insuring that no damages can ever be legally proven to be due to failure on your part. The AllPacks manager system is based their patented EDND (enormously deeply nested dependencies) technology.
6. The UE is considering legislation making it illegal for software companies to require developers to understand the tools and languages they are using, calling it 'part of a discriminatory and elitist past.'
Explorans limites defectum
modified 9-Apr-19 21:06pm.
|
|
|
|
|
Ain't you 9 days late?!  
Other than that C++ 21 looks very promising! 
|
|
|
|
|
oo u must be working at apple or Microsoft ... or at google making android ...
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
Pah.. forget Android man!
The future in Mandroid!
|
|
|
|
|
'4. Containertainers, it's so 2019!
I think Contertainers are much better! 
|
|
|
|
|
Intratainers?
Explorans limites defectum
|
|
|
|
|
Compress your containers into a concertainer.
We're philosophical about power outages here. A.C. come, A.C. go.
|
|
|
|
|
Dean Roddey wrote: 4. Containertainers. Managing all of your containers and their options is now becoming a serious challenge to many companies. Containertainers are containers for your containers and their configuration operations, simplifying your container deployment and management process. Work is already under way on Containertainertainer technology, in anticipation of projected containertainer deployment growth.
I'd call these 'shelves' and 'paint pots'
|
|
|
|
|
Absoultely let's do things the modern way, where we have 10 layers of boilerplate to write/use before we can do anything:
View
Controller
Interface for the controller
Orchestrator
Interface for the orchestrator
Repository
Interface for the repository
Model
Interface for database access
Client for database access
I feel sorry for the young'uns nowadays having to learn this mess.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
Ah, the onion... lots of layers and tears!
|
|
|
|
|
I'm trying to complete the "order" to receive my money for the Slack competition, and I keep getting
"We're experiencing technical difficulties
We're sorry for the inconvenience."
For days now.
Latest Article - Azure Function - Compute Pi Stress Test
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
slack: adj.loose, baggy; inactive
Maybe they still wanna win?
|
|
|
|
|
I can lend you a fiver, if you're short.
i.e. if you're tall enough to go on all the rides, forget it!
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
|
I think it is, for the most part. His whining about compile times is understandable because most people don't seem to know how to write header files with that in mind. PIMPL being not used enough is another cause.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
Sure, I can't use either 
|
|
|
|
|
Modern C++ is very complex and the bulk of people who use it probably don't understand half of the details.
It's vastly over-templated. It's not really possible to keep build times low when you have enormous amounts of templated code in a large code base because all that code is inlined.
A lot of folks in the 'modern' camp seem to have convinced themselves that inheritance is evil, and will jump through fairly ridiculous hoops not to use it, using horrendously ugly stuff like the standard variant stuff and basically doing what OO was invented to avoid (lots of switch statements everywhere, and standard variant is just a particularly ugly switch statement.)
A huge amount of effort was spent creating a seriously over-engineered container system, while leaving fundamental stuff not dealt with, and leaving C++ in a situation where even now you can't write even a modest practical application without third party libraries.
Explorans limites defectum
|
|
|
|
|
Well.. C++ multiple inheritance is always full of surprise, isn't it?! 
|
|
|
|
|
Dean Roddey wrote: you can't write even a modest practical application without third party libraries.
I respectfully disagree. I've written several useful utilities using "pure" C++ (and the standard library.) Adding third party libraries make it even more rich, as it does with every language, including Python.
I'm now working on a server which uses asio, rapidJson, OpenSSL and LZ4 and SQLite. However, the majority of the code is "straight" C++.
|
|
|
|
|
I'm not sure I'd consider a utility to be a practical end user type application. Anyhoo, it's at a significant disadvantage relative to languages like C# or Java that have far more built in functionality. And it's far less likely that your experience working on project A will apply to project B when you move to another company.
Explorans limites defectum
|
|
|
|
|
Dean Roddey wrote: And it's far less likely that your experience working on project A will apply to project B when you move to another company.
Quite to the contrary. My C++ experience has transferred extremely well through the recent years and multiple contracts/short term jobs. In my most recent project, I easily cut months (no exaggeration) off the development time because of this.
|
|
|
|
|
Dean Roddey wrote: I'm not sure I'd consider a utility to be a practical end user type application.
I'll let my users know
|
|
|
|
|
Dean Roddey wrote: while leaving fundamental stuff not dealt with
Like what?
|
|
|
|
|
Language-wise decent enumerations would be a big one IMO. Otherwise, a vast swath of functionality that things like C# has built in that are important to most practical applications. Sockets, text transcoding, loadable resources, XML, JSON, HTTP, MVC, graphic file formats, image manipulation, a good streaming system, RPC of some number of types, and on and on.
Look, don't get me wrong, I probably have 10 times the vested interest in C++ than all of you put together. But as it stands right now, it's got problems.
I know what it's like to work in a C++ system with all those things and much, much more since I've created one. That's what C++ should be like by now.
Explorans limites defectum
|
|
|
|
|
Dean Roddey wrote: a vast swath of functionality that things like C# has built in
were written in C++.
What's your point?
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
