maximexx
Nice one for the indie developer. It looks like the PIA can take more time to get right than your actual program..
Sometimes I take more time to think of a proper and scalable name for variables and methods than the time it actually took to write the implementation. While refactoring I might do another round of thinking about naming and make sure there are no or an absolute minimum of possible side effects for the implementation, etc..
I'm coding almost 30 years now. I'm still learning and make my mistakes of course, but most of the time they occur because I rush for some reason. Writing good code takes time, especially to rethink what you're doing, refactoring, making the right adjustments so it completes the codebase. Before I complete the beta release of a codebase I've made thousands and thousands of decisions, where only 1 wrong decision can cause a terrible amount of trouble later on.
For me it's a creative process. It goes in waves. I cannot always be a top performer, I've accepted that. When I recognise I was in a low during some implementation I might do a total rewrite of it or apply some serious refactoring(and force myself to take the time for that).
I still experience coding to be much harder to get right than I ever expected it to be. For me a codebase is a highly complex system of maybe hundreds of files with API's working together, not just a bunch of algorithms.
No. I suggest focussing on explaining concepts, not drilling sums. And explain them why in ancient times the teacher used to use a cheat sheet because drilling didn't work because science found out our minds are not wired for that.
Besides, from over 7 billion people on Earth, how many need Algebra 2? Please try to be honest and give us here an estimate teacher. In your life Math is important apparently, but in most lives it's not. Teach it to those interested please and don't push it through the throat of those not interested.
IMAO the current system of teaching math is ancient and above all deprecated. We should not punish our kids with it. I mean, what's the point of drilling stupid sums if you'll hardly ever need it in your life? I think it is totally stupid and irresponsible if anyone does calculations without a calculator for almost any application, not excluding: store checkout, health care, aviation, etc.. The current educational methods are way pre-computer era, it desperately needs an upgrade.
So why not start teaching kids concepts and let them use the technologies we create to solve problems that our minds are not wired for? Ever seen a teacher without a cheat sheet checking the answers? Guess why? Because their own calculations are too slow and above all not to be trusted! And should I not use a debugger because theoretically we can write proper code without it? Come on..
Please stop teaching our kids deprecated workflows. Teach them the best practice, the best way we know and can do now, because: "As the twig is bent the tree is inclined".
No, it's not. Promises suck, that's all, no need to spend more words on it.
No, just totally ditch them!
I can't help to hate Promises. Sometimes I have to work on a code base that is completely baked with them, it's just a nightmare. With the stupid async await implementation things haven't got any better.. Now they expect me to write async calls in a try-catch block!?!
With JS I prefer to use simple callbacks until they come up with a proper async await without try-catch and Promises bullshit. Callback hell happens not because of the callback principle itself. It exists because it's too easy to keep nesting functions. Most devs simply don't know how, or are too lazy, to apply good patterns for using callbacks.
Still, it's good to keep a sharp eye on Canonical. I have not forgotten about the "lens" sending your local query to 3d parties like amazon by default..
The educational system.
I've seen horrible things happening to production code due to junior developers. In the end the senior/lead needs to spend way more time fixing all bad code/ideas than if he'd write it himself in the first place. I know a company that has a medior dev that is now already more than 2 months working on a feature I can write in just 2 weeks. Besides that, my code will likely still be better because I code with experience, using proven strategies, making it more scalable, preventing pitfalls, potential bugs, etc..
I don't think the companies are to blame. A junior dev should not write rubbish if he/she is a software developer graduate. Current IT education is very limited. Most of the things you learn in 5 years can be interesting and a good foundation, but not really relevant for most developer jobs out there. You actually have to start learning to code once done with your study. And learning to code is not a short journey, I guess at least some 3 years of full time study before you'll get the hang of it. And I didn't even touch the idea that you definitely need some talent or feel for it. You can study arts, but that alone won't make you an artist.