Earlier quoted context omitted.
It will be, we just need a couple more lawsuits about faulty software and security exploits.
How long has this sort of stuff been said though?
If You're Not Writing a Program, Don't Use a Programming Language [video]
251–260 of 288 posts
Re: If You're Not Writing a Program, Don't Use a Programming Language [video]
#252Earlier quoted context omitted.
> I haven't fully learned Rust yet but from what I understand, the borrow checker only applies to mutable data This is not correct. The borrow checker applies to references , both mutable and immutable.
I think the intention was that if you have no mut refs, then you have no borrow checker problems.
Re: If You're Not Writing a Program, Don't Use a Programming Language [video]
#253Earlier quoted context omitted.
I agree. People obsess about the choice of programming language, insisting that months of study are needed to choose. I just don't see it except for very specialized tools or applications. That said, I find maintaining an old, large application written in an untyped language pretty miserable.
I've had equal misery both typed and untyped on large, old, legacy stuff. Maybe programming just sucks.
Re: If You're Not Writing a Program, Don't Use a Programming Language [video]
#254I'm more with Mike Acton in this respect; the hardware is the platform, not the software. And in that sense... In order to really make good use of your hardware you need to understand your hardware and code accordingly. I doubt you can achieve great performance on a language that focuses entirely on mathematical representations without considering the hardware. So yeah... you end up with a beautiful mathematical expr…
You can do both.. But it is hard.. https://www.youtube.com/watch?v=zt0OQb1DBko
Re: If You're Not Writing a Program, Don't Use a Programming Language [video]
#255I wasn't exposed to spreadsheets until a few years into college back around 1996 or 1997 maybe (I had been programming in C/C++ for 7 or 8 years by then). I wasn't taught matrix math until pretty late in the curriculum, I want to say junior or senior year. Also I was lucky to have a semester of Scheme but they were transitioning to teaching Java around the time I graduated (I don't know if they ever switched back). A…
I disagree that they should phase out imperative / OO programming, but from my experience more emphasis on different languages i.e. throw in a ML (as in Meta Language) and a Lisp, and most importantly some information about the trade offs. However it would require a culture shift as a university being a place to get you ready for a career in industry rather than academia. Because you are prepping for academia it is O…
And that's why I despise code reviews. There's obviously not enough time allocated to them for in-depth understanding of the reviewed code, so I'm mostly spending precious resources (attention, energy) on doing a half-assed review that is not going to do that much good. It feels like such futile work.
Re: If You're Not Writing a Program, Don't Use a Programming Language [video]
#256Earlier quoted context omitted.
I think that tools such as TLA+ show their value not by convincing people that they're worth the extra effort but that they actually save you effort. The experience at Amazon and Microsoft shows exactly that, and managers were relatively easily convinced.
Absolutely agree. I work in the autonomous vehicle space, specifically in creating high-assurance resilient systems, and I've had more arguments that I care to count which went something like the following: Them, "All that extra effort sounds great, but we don't have the time to do that. It will explode the really tight build, test, debug cycle we have now. Suddenly every cycle will be 100x as long." Me, "First of al…
That's why I'm sceptical about going to work on the autonomous vehicles tech (although it is tempting). I'm affraid there's been so much money and hype around it that "failure is not an option" - i.e. companies will sooner see another Challenger disaster than admit that they're not on track for their announced goals.
Re: If You're Not Writing a Program, Don't Use a Programming Language [video]
#257I wasn't exposed to spreadsheets until a few years into college back around 1996 or 1997 maybe (I had been programming in C/C++ for 7 or 8 years by then). I wasn't taught matrix math until pretty late in the curriculum, I want to say junior or senior year. Also I was lucky to have a semester of Scheme but they were transitioning to teaching Java around the time I graduated (I don't know if they ever switched back). A…
>Honestly I think it might be time to phase out teaching imperative and object-oriented programming. I have seen plenty of universities teach Java and C++, haven't seen any that teach actual OOP. James Coplien aptly calls the current paradigm "class oriented programming".
Stop reading here.
(Since Bertrand Meyer, driving force behind the language and course, retired, the course is now taught using Java.)
Re: If You're Not Writing a Program, Don't Use a Programming Language [video]
#258Earlier quoted context omitted.
How long has this sort of stuff been said though?
Not long enough, but IoT mass deployments are going to change that, as they are much worse than Windows 9X security issues.
Re: If You're Not Writing a Program, Don't Use a Programming Language [video]
#259Earlier quoted context omitted.
"It's quite likely that during their lifetime, machine learning will completely change the nature of programming." - Why is this the case? Even if it's true, it hardly seems obviously true.
Because soon you will just ask your computer to build your code after giving it a few parameters. Then you will proof read and sanity check the code and spend more time optimizing and working on the really hard problems.
On the contrary, I think machine learning might be more immediately useful for things like low-level optimization.
Re: If You're Not Writing a Program, Don't Use a Programming Language [video]
#260Earlier quoted context omitted.
Absolutely agree. I work in the autonomous vehicle space, specifically in creating high-assurance resilient systems, and I've had more arguments that I care to count which went something like the following: Them, "All that extra effort sounds great, but we don't have the time to do that. It will explode the really tight build, test, debug cycle we have now. Suddenly every cycle will be 100x as long." Me, "First of al…
> It's become more important to produce the appearance of progress and effort than it is to actually make progress and thoughtfully apply effort. That's why I'm sceptical about going to work on the autonomous vehicles tech (although it is tempting). I'm affraid there's been so much money and hype around it that "failure is not an option" - i.e. companies will sooner see another Challenger disaster than admit that the…