Comments by "disgruntledtoons" (@disgruntledtoons) on "ThePrimeTime" channel.

  1. Fast-to-ship frameworks are how we get unmaintainable apps nowadays: 1. Slap together a demo of the app. 2. Management: "How quickly can you put this into production?" 3. You: "That cannot be accurately predicted." 4. Management: "I need a clear time-frame." 5. You: "At least four sprints." 6. Management: "Have it ready in two sprints."
    480
  2. There is no getting around the fact that querying a relational database is a fundamentally different thing than just about everything that doesn't involve the DB. One language isn't enough if you care at all about getting the best performance out of your system.
    91
  3. C was created by engineers who just wanted to get stuff done. After creating it, they used it to get stuff done.
    23
  4. Python is the new BASIC. You use it for testing new ideas. If you need better performance, then you re-implement in a more performant language.
    2
  5. In the use cases where C is superior to other higher languages, assembler is better still and no less safe.
    1
  6. DRY best applies then the operation that is repeated has to be done the same way in every instance. Then you break it out into a new function.
    1
  7. The project you should try is one that uses technologies that you don't already know. I'm writing a web site in Angular, Node.js, and MySQL because I had not used them.
    1
  8. Time for HTML6!
    1
  9. The reason for uncanny valley is there can only be one top priority, and everything else is nice-to-have. Either performance is sacrificed for dev velocity or dev velocity is sacrificed for performance.
    1
  10. I went to a job interview yesterday and everybody working on software had seen something like this.
    1
  11. What we're going to see is a spate of bean-counting managers try to replace developers with AI, and getting some things done but other things done in a half-assed way, and eventually hiring a real live human to do what the AI can't.
    1
  12. A person only needs to know, off the top of his head, things that are used at least monthly. For everything else, there's Stack Exchange.
    1
  13. "Write in C, write in C..."
    1
  14. Tomorrow morning a new developer will report for work at the company where I got my first job. Part of his on-boarding will be to learn COBOL.
    1
  15. Linked lists are best when you want to implement a highly performant LIFO queue and never need to access anything but the last item added.
    1
  16. Any dev org which puts front-end and back-end on separate teams is going to have troubles. Full-stack devs are forced to understand the whole process. There is no substitute for knowing the whole process.
    1
  17. I hate the term because it is a horrible description of what it does. "Library importation" would be a more precise term.
    1
  18. I like how everyone talks like C is the the lowest level of programming. Those of us who coded apps in assembler are a bit smug at this.
    1
  19. The worst person at any stage of software development is the person who makes things more complicated than they need to be. Needless complexity is the enemy.
    1
  20. It's the same as with any other framework. No framework does everything that can be done with the underlying layer of the tech stack, and someday the requirements will go outside of the framework's box. You will need to know the underlying layer in order to code the work-around. With some frameworks the need to work around a limitation is so pervasive that you're better off not using the framework at all. And when you need a new developer to replace the guy who just won the lottery or got hit by a bus, he needs to know both the framework and the underlying tech layer. That's a greater delay and increase personnel costs.
    1