Comments by "Brent Jacobs" (@br3nto) on "ThePrimeTime" channel.

  1. Saying that, the issues with dynamic languages that Prime talks about are there… how is this method used? If I cache this methods implementations or return value, what will break? Now that I’m fluent in both languages, I can say with confidence that it all evens out in the wash… the effort it takes to refactor all the code using my method in static typing vs just accounting for and normalising the the ways my method is being used and adapting to that is same same. As always, the things that really matter in the end is: is the code easy to test, easy to maintain, easy to understand. If any of those things are false in a typed or static language then things will go bad.
    1
  2. 0:41 I’m sorry for you for what I’m about to do and I feel slightly guilty about it I think is the full saying
    1
  3. This is really where you break the problem down into smaller steps. Yeah it can create a performance hit, but it makes understanding and verifying the code so much easier regardless of debugging method. Single lining everything makes code difficult to debug.
    1
  4. 16:55 are you gonna raw dog calls to Redis, or your favourite pub/sub broker, or to HTTP clients/servers? No? Then you don’t need to raw dog SQL either. We don’t need to put databases on some magic pedestal and give it special treatment. They are just another way of persisting data.
    1
  5.  @ThePrimeTimeagen  sure, not by itself. I think it gets compelling when combined with my other counter-points.
    1
  6. 2:58 this is the same as the promise of cloud solutions 😂
    1
  7. 19:50 same promises made for cloud services
    1
  8. 9:45 even when you write SQL you don’t know what the query plan will be unless you inspect that, so why is it a problem that you don’t know what the SQL will be unless you inspect it? Optimisation is maybe eventually needed whether you use SQL or an ORM, so it really doesn’t matter.
    1
  9. 26:38 it’s not that there is a higher level of okness… we have limited mechanisms to provide feedback and limited time to respond to or handle feedback. Even if we do have feedback… it gets dropped into a backhole… who knows if any dev team ever sees the feedback? Does the dev team even have to time to prioritise this one little thing over all the other little things they have to do?
    1
  10. 11:31 that looks like nightmare code 🫣🙈
    1
  11. 5:15 this same argument could be applied to actual programming too… how much time is wasted tweaking and configuring and designing code to feel and look good that doesn’t actually progress the task towards completion. This work is good at first, but suffers from diminishing returns over time.
    1
  12. 12:49 the application is the owner of the database and therefore it is the perfect and only place migrations should exist. Databases shouldn’t exists as first class entities.
    1
  13. 0:28 a company can be a cooperative and prioritise some other value. Usually increasing profitability will still be a key metric in increasing the primary value.
    1
  14.  @arcanernz  that’s a fair point, but cutting corners now always leads to more pain later. It’s a trade off the developer chooses to make (unless they lack the skills to make better choices). The pain will be experienced by whoever needs to modify that code in the future and the metric of pain is how difficult it is to make that modification. I guess it’s easy to criticise code for not considering some future requirements. But there are some objectively good and bad patterns of writing code that are harder or easier to change. So a developer struggling to get code out the door could still opt to prefer the good patterns vs the bad patterns.
    1
  15. Not all dynamic languages are the same… Ruby like small talk, is about dispatching messages to objects which can either handle or not handle that message. It’s the ultimate event driven language. Dynamic languages like Ruby is about processing and transforming data. It’s a totally different paradigm to typed languages.
    1
  16. Ps python is not that great
    1
  17. 18:07 learning react is actually super easy. Takes no time at all… almost not worth the time. Hooks also introduce a lot of laziness I’ve noticed.
    1
  18. 2:55 python is one of the worst languages ever 🤮 Successful but horrible. I think it’s success comes down to Jupyter notebooks, which made it super accessible and useful for code exploration required when prepping data for analysis and AI. If you’re developing a language and want to compete against Python: First, recreate Jupyter notebooks for your language. A REPL won’t cut it because it isn’t shareable. Next, create wrappers for all the data science and AI c libs. Finally, create a transpiler to transpile python to your language.
    1
  19. 4:54 the thing to remember is that LLMs will allow humanity to cross domains of expertise when previously that expertise was siloed. So even though it can’t come up with anything new per-se, it could help connect a lot of dots that haven’t been connected yet. That will take many humans a while to surface and then make practically useful.
    1
  20.  @Shm00ly  like everything, it’s a spectrum. People are multi-faceted and have multiple interests and are able to grow out their interests. If someone thinks there is a connection between something, they will seek it out, regardless of whether anyone else believes that connection exists or whether or not they believe that person can do it. It’s not going to be the everyday person that makes profound connections. It’s going to be the curious people, the entrepreneurs, the explorers and adventurers, the brave. Most people will probably just stick to their niche and maybe explore a little beyond within the bounds of what’s already been explored.
    1
  21. 10:03 yeah that’s long. Very verbose. Lot of text for not much.
    1
  22. 7:10 that sounds like a 💩 way to write software
    1
  23. 5:15 I don’t like that take either. It makes you feel good to say, and ignore evidence to the contrary.
    1
  24. 10:27 they’re describing the same same job, same degree, same qualifications. 🤷‍♂️
    1
  25. 9:44 they started at 57000
    1
  26. Isn’t d a Roman numeral?
    1
  27. I guess people rewriting code and making new libraries instead of using the existing ones for what ever reason, is no different from companies bringing out new models of TVs and cars and washing machines and any other type of product you can think of. It’s how innovation occurs, and it’s how we move away from the over engineered legacy systems and software.
    1
  28. This is why I try to convert personal knowledge into institutional knowledge. Similar to replacing resources with processes. Processes are repeatable.
    1
  29. You can do closures using classes. If you squint they look the same! 0:36 I hope he says that…
    1
  30. 0:54 no!!!! Just close over the local scope by instantiating a class, then pass around the instance, then call the method on the instance!
    1
  31. 22:08 Raw JS is super useful!!
    1
  32. 19:35 OMG did you just suggest they introduce a build system so they can support IE11? That completely defeats the choice of not having a build system. You either do or you don’t.. there is not inbetwix. I guess some people just get stuck in a particular mindset
    1
  33. 28:58 you’re starting to sound a lot like DHH 😂
    1
  34. 3:22 I also look at their issue velocity. Do they leave issues and merge request open. Oh and commit history. Stars first though.
    1
  35. Charge $100 per bug report as a deposit. Then deposit + bounty returned when bug is confirmed.
    1
  36. 33:53 “value simants”?? What’s he saying??
    1
  37. 5:47 doesn’t Visual Basic do that?? Pretty sure that’s how you do things in VBA for Excel.
    1
  38. 12:57 Java applets were awesome! Basically Flash, except it’s Java! Basically like the HTML canvas, but Java! Can we still do applets?
    1
  39. 7:32 stolen from Ruby!!! Ruby does this too. It is a very cool useful feature!! Works well not just with DSL building, but also iteration. It’s kinda like continuations.
    1
  40. 8:02 Ruby also has syntax so you can pass objects to the block (Ruby calls trailing lambdas, blocks, and you take different actions whether the block is defined or not). I assume Kotlin would have similar syntax. Usually you would pass in builders or configurable options to the block that you can set inside the lambda. But Ruby also allows you to set the scope of the block to some other object, or to marshal calls to some other object. I wonder if Kotlin allows you to do this too.
    1
  41. 9:08 oh it looks like you can do that I. Kotlin too!! Awesome 🎉
    1
  42. 7:30 you should have a degree. I wouldn’t hire anyone without a degree because they are guaranteed to be missing foundational educational required to write quality software.
    1
  43. 2:49 Ruby is waaay better
    1
  44. 3:12 cmon, you can dunk Ruby in the C too
    1
  45. 5:47 booo! Don’t poo poo Ruby. It’s actually awesome.
    1
  46. 18:59 SQL isn’t just a string literal. It’s really no different in concept from sending shaders to a GPU or sending bytecode to a JVM, or instructions to a CPU, or a request to an API.
    1
  47.  @isodoubIet  sure, but that’s a different issue to the string literal comment.
    1
  48.  @isodoubIet  how?
    1
  49.  @isodoubIet  how is it “exactly the issue”?
    1
  50.  @isodoubIet  it’s not just a string though. You can’t just write anything. It’s a declarative language that is literally interacting with the API of the database schema and/or database engine. It’s pretty much the same as calling an HTTP server, or Redis, or a GPU, or a CPU, or sockets, they are all one thing getting another thing to do something using 1s and 0s.
    1