Comments by "Toby" (@toby9999) on "Continuous Delivery" channel.

  1. My CS Degree was in no way "a branch of math". There was a math prerequisit because marh is used in CS and in software engineering. To me, the difference between CS and software engineering is that CS teaches a much deeper understanding of computing, whereas software engineering is much more like job training. I know this because my degree included both, but the CS component was much more valuable to me even now, 30 years on and retired. My son is now in a software engineering course at a local university, but he's not being taught computing. He's being taught full stack web development and how to write tickets and do branching in Git etc. and how to run meetings and a bunch of languages and frameworks that, in a few years, will be tossed aside. This is all the kind of stuff any decent CS graduate can pick up on the job. Nothing I learned in software engineering was ever of great value, whereas my CS knowledge is timeless. For example, we learned how compilers work and how to design them. We studied AI techniques in depth. We studied the theory of computing and the structure of languages and language types and their pros and cons. And as an interesting side note... the only students in my son's group project teams that have any clue at all are the CS students. We must not forget that university isn't supposed to be job training. It's academia. It's where the deepest knowledge in a specific field is learned.
    7
  2. I've been a developer for 30 years and have never heard of "BDD". Is it really all that popular?
    6
  3. I would have hated it. A complete waste of time. I prefer working on my own. If I need help, I ask, but that's it. And also, fortunately, I had a great manager. But, the industry is full managers who try to introduce stupid ideas such as peer programming and other nonsensical ideas. I'm out of the industry now. It was great when I started almost 30 years ago, but now... not really.
    3
  4. Same for me. I just don't relate directly to people when they're in my space. I just switch off mentally. Must be the aspergers in me. Fortunately, we all started working remotely in 2020, and I loved it.
    3
  5. Eclipse would be an absolute nighmare, especially for beginners.
    2
  6. I've been a C++ programmer for 30 years. I love it. Flexible, powerful, and performant, and implementations build native executables by default. I agree with your approach to OOP. It's a tool, but it shouldn't dominate.
    2
  7. I hate the JVM conceptually. I also hate .NET conceptually. This is why I have an extreme dislike for any language that runs on these subsystems. Java being the most obvious one. The promise was to be platform independent. Then why develop a Windows only application in Java for instance? A lot do, and it's stupid. I even know of cases where a Java application is converted to native code. How silly is that? Why even bother making a desktop application cross platform when 99% of potential users run Windows? It's bloat. That remaining 1% may as well buy a Windows machine and have a better more performant application running natively. The most powerful platform is the hardware. Every unnecessary layer added on top is bloat.
    1
  8. Not sure why anyone would propose rapid fire commits. Why are people doing rapid fire commits anyway? People committing junk instead of finished work makes no sense to me. This constant committing seems to be a Git thing. I'll never commit anything unless I consider it completed work by some sensible metric.
    1
  9. I hate it. Been using SVN for 15 years no problem. Now Git has me tied up in knots. Git just wastes my time. Understanding Git is harder than the C++ development I'm actually paid to do. It's a nighmare.
    1
  10. It depends on definitions, but before watching this video, my opinion is craftsmen. Software development is more an artform than it is engineering. The definition of "craft" that best fits my usage here is "an activety requiring manual dexterity or artistic skill".
    1
  11. Git is just awful. I'm a great believer in KISS keep it simple. Git is all about making it complex. All of this Git branching and merging creates more problems than it solves. I prefer SVN and a single branch approach I refer to as continuous merging. Regular updates keep my local copy up to date. No need for dozens of separate feature branches. Too many of them sit around for days or even weeks and cause horrible merge issues anyway. Additionally, code sitting in a feature branch is not available to the team and can cause delays. This never happened until we switched to a new fangled Git process.
    1
  12. I've been doing OOP for 30 years, but as time goes by, I dislike it more and more. Why? Because of the overuse of abstraction. Legacy C code is starting to look appealing due to its simplicity. My comfort zone right now is C++ but with a little less emphassis on OOP. Perhaps more of a "C with classes" style. I did get some exposure to Jave code bases, and they were absolutely diabolical. OOP on steriods. The class structures almost incomprehensible.
    1
  13. OOP is a useful tool when used correctly and carefully, but very often, what I see is as bad as the old BASIC spagetti code if the 70's i.e. OOP often leads to way too much abstraction. Sometimes, there are too many small classes or or class methods that do nothing of value but add to cognitive load.
    1
  14. The whole java development environment and ecosystem sucks big time, and some bits suck more than other bits... Eclipse IDE should probably head the list in terms of crapware. Even the Eclipse Foundation effectively admitted that there were serious problems related to usability and market share. Taken as a whole, java has been the worst language / dev environment I've encountered in my 30 years of coding. C++ is my favourite by a massive margin. If I had to choose 2nd place, it would be C. And no, I am not battle worn. I very rarely have problems with pointers and memory. And no, java is not as performant as C/C++ or Rust and a few others in the sane class.
    1
  15. It's both. It's a less than perfect idea implemented badly.
    1
  16. In the real world, refactoring on a daily basis is not desirable, at least not unless you're working on a new product and/or the code must be refactored. You don't code anything unnecessarily in anything mission critical, and the code base I worked on for 20 years was all mission critical.
    1
  17. Why do you need to push stuff that isn't done? I only push/commit finished work. This is how I've worked for 25 years without issue.
    1
  18. My wife is into craft in a big way... water color painting, patchwork, sawing, cake decorating, cross stitch, baking, teddy bear making, doll making, etc. Not much engineering happening.
    1
  19. I like it within a feature branch. Don't bring the useless crap into the main branch.
    1
  20. ​ @IronCandyNotes That's loudicrous.
    1
  21. OOP encourages encapsulation, and that in turn too often encourages unnecessary structural complexity. Too many deeply nested methods make code difficult to follow. I would rather have a hundred lines of code visible on screen than have it broken up into numerous function calls.
    1
  22. I've been a C++ developer for over 30 years and professionally for over 20, and that has never happened. Perhaps some specific version of a dodgy open source compiler, maybe? To say "all the time"... I can't take that seriously.
    1
  23. Learning a programming language can be a major hurdle. I've used many languages over the past 40 years, from machine code to Lisp to Ada to Pascal, C and C++, and others... but I could not transition to Java. Complete fail. I just couldn't get my head around the language and ecosystem. It just sucked.
    1
  24. Phantasy? If you meant fantasy, then no. We effectively do have total control, i.e.. we're not bound by the kind of physical limitations engineering typically deals with. That's what was meant, obviously.
    1