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

  1. Technically, going from 0 users to 1 user is an infinite growth rate. VCs will cream their pants over infinite growth.
    646
  2. That c++ refactor was the most ridiculous and hilarious thing I've seen in a while. I burst into laughter at the exact same time Primagen did.
    637
  3. "Mindful" for "async" and "holup" for "await" were good suggestions I saw scroll by in the chat.
    515
  4. "Everyone does things the convoluted serverless way that I do things, and I don't find goroutines useful, therefore goroutines are useless to everyone."
    312
  5. I realized after returning home from a three week cross-country driving journey that I needed to organize my tasks, but my kanban instance has been broken for a few months, so I thought "I should make some kind of app". Then I realized that I didn't have 20 hours to spare before getting shit done, so I thought "I should just use an Android to-do app". But then I realized that fixing my phone was one of the tasks and might involve a data wipe, so a to-do app would not work (and besides, they all suck). Finally, I had an epiphany: I grabbed a piece of paper and a pen. This mental clarity would not have been possible had I not given up writing JavaScript.
    301
  6. I think that my #1 piece of advice for programming is simply to be prepared to throw out code. Attachment is a vice one must shed on the path to enlightenment -- pragmatically speaking, the first time you implement something, it is likely to be shit; improvement requires flushing it away.
    218
  7. “I used to say that when being CEO at Apple wasn’t fun anymore, I’d quit. But now I’ve changed my mind — when being CEO isn’t fun anymore, I’ll just fire people until it is fun again.” -- Michael Scott, CEO of Apple, regarding the massive layoffs undertaken to solve the bozo explosion, a few months before he got fired for it
    184
  8. I'm glad that the Aqua Team Security Nautilus Force is out there fighting cyber crime.
    148
  9. I have a friend who works as a technical product manager. He told me that he has had to fire some devs for performance issues, and he said that he had to first put them on a performance plan for a few months before being able to fire them, but the decision had already been made, so the result of the performance plan didn't matter -- it was just some corporate bullshit that had to be done to cover the company's ass.
    146
  10. Idea: snake_case variables are heap allocated (because snakes are found in heaps of wood, etc); camelCase variables are stack allocated (because camels travel in straight lines, like a stack pointer); camel_Snake_Case variables get instantly deleted because it's a terrible way to name a variable.
    139
  11. I tend to write code twice: the first time, I just play around in a scratchpad repo with spaghetti; the second time, I structure the code more sanely and add tests. The second iteration can be TDD because by then I've figured out what I want the code to do.
    138
  12. Moral of the story is to put effort into the backstories for your D&D characters, especially if they are supposed to be speakers at your tech conference.
    80
  13. I love the box I live in. I think inside my box. It's a comfortable box. Nothing exists outside of my box. Outside of my box is the Satan. Therefore, anything outside of my box either does not exist or is evil.
    79
  14. Life is a lie, there is only code. Through code, I gain work. Through work, I gain projects. Through projects, I gain junior devs. Through junior devs, my compilers chains are broken The code will fuck me.
    74
  15. I just checked the Wayback Machine archives. The trademark policy was changed September 25th, 2024. The day prior, the original policy was still there and had been unchanged since September 2010. Edit: it was actually changed halfway through September 24th.
    67
  16. Phone glitched out literally as the video ended and caused my Discord app to send an autoreply agreeing to something when I tried hitting the like button. This dude is right: fucking machines need to be told what to do and stop telling us what to do.
    65
  17. Similarly to how animals tend to evolve into crabs, code for any project with sufficient longevity evolves into spaghetti. AI just skips a few generations and gets you to the spaghetti crab faster.
    62
  18. I have been using Python to make reference implementations of stuff I found in math and computer science papers for a while now. Great language for doing that. For example, I recently created a genetic algorithm library; I started in Python, then reimplemented in Go; Go was more performant by a wide margin even before I refactored to use memory pools (which resulted in a 99.94% reduction in benchmark times for simple use cases).
    56
  19. One step closer to the Empty Internet. Soon, someone will hook up an LLM to write issues and comments in issue threads and even some shitty broken code repositories, then hook it up to a finite state machine and some other shit to add emoji reactions to issue comments, and then let it smolder in the background for a few years on a thousand bot accounts. And when GitHub strikes back, there will be casualties, and actually useful code will get deleted.
    47
  20. COBOL is the language with the power of Chronos/Saturn: it is the past, the present, and the future. The majority of the global financial system uses COBOL. Let that sink in.
    46
  21. I remember the days when EcmaScript didn't even have proper classes. Back in my day, we used functions named in PascalCase and then prefaced calls to them with the "new" keyword.
    46
  22. My most fulfilling work is stuff I do on my own initiative. The stuff that people ask me to make tends to be boring and frustrating shit.
    44
  23. Sounds like the guy just doesn't understand what he's talking about. Goroutines are useful for both concurrency and parallelism.
    34
  24. The latest VS Code update included a "bugfix" which was actually a feature change: instead of leaving Python docstrings highlighted as strings, some guy created a pull request that changed them to be highlighted as comments, which is incorrect. There has been a lot of pushback for suddenly changing all the themes in VS Code to incorrectly highlight docstrings. The guy thought he was correcting a wrong behavior, but it ended up being just his personal preference being foisted upon everybody else. So now there is a pull request open to revert his change, and there is an issue about making docstrings and block comments separate tokens for highlighting purposes.
    32
  25. The best example I've seen in a while of congratulations/I'm sorry.
    27
  26. Based and nontoxic.
    25
  27. Slow decline was probably saturation: after the same question has been asked and closed as a duplicate a few hundred times, the number of links pointing to the answer will be high enough that you're likely to just find the answer instead of having to ask it another time. That's my theory. Edit: also, the toxicity of SO was a likely factor. That was the reason I stopped using it: arguments with power-tripping mods who arbitrarily edited my questions and temporarily banned me for having the audacity to want my contributions to be a certain way.
    23
  28. "Anonymized browsing data" is like "we put our users in a blender and sold the slurry, so it's okay".
    22
  29. The entire concept of "continuous delivery" seems to be something like "discover footguns as quickly as possible by firing them as many times as possible in production systems".
    21
  30. ​ @AdamPippert possible duplicate comment. Closed for being off-topic and opinionated.
    19
  31. That story about the backends being cached bytecode sounds scary similar to JDSL.
    17
  32. Update: after 2 months, the change was finally reverted.
    17
  33. "Overwhelmed with complexity" is a generally good description of writing frontends with React.
    15
  34. When I was in high school, I was a tech aide for the head IT guy, and there was a precedent established over the previous few years that the tech aides were hackers. I and my fellow tech aids continued that legacy but we were far less disruptive and more responsible with our shenanigans, and we reported everything we found (eventually). Fun times. The closest I got to being in trouble were a couple of experiments that I forgot to clean up at the end of a period and had to go manually fix, but I was constantly being sent around the school to fix things anyway, so it was never a big deal -- just a "go fix it, and don't do it again". Edit: spelling
    15
  35. Fearless cost abstrurrency. Rust isn't a cult. It's a Foundation™
    12
  36.  @xelspeth  I don't write JavaScript. I gave that up. Did you not read the original comment? You just want me to relapse. Imagine what that would do to my family.
    12
  37. Redoing crates to have a hierarchical namespace is an ongoing discussion in the Rust community, unless they resolved not to do it within the last couple of weeks since the last time I read about it.
    11
  38.  @ficolas2  they'd be constants, not variables
    11
  39. Python > JavaScript unless you need to do stuff in a browser or build something you should have built in Go.
    10
  40.  @spankyjeffro5320  the performance plan thing only applies to those who do not do what is required of them. The job requires X and they don't get X done, so they get fired with extra steps.
    10
  41. Clearly, the time has come for an HTML vs Zig comparison article written by ChatGPT.
    9
  42. Brondo* has the electrolytes that plants crave.
    9
  43. I do not like Rust as a language, but the nuanced discussions around memory management brought about by Rustaceans are great. I've implemented several bespoke virtual machines for creating compact cryptographic proving systems, but they have not had anywhere nearly this much detail in their memory models.
    9
  44. @defeqel6537  definitely. And this also implies writing code in a way that is easily testable so you know what code to throw out.
    9
  45. The runtime is configurable but uses 32kb of memory by default. This is very much not simply JavaScript on an embedded device -- this is more akin to compiling TypeScript to a small form of embedded Java.
    9
  46. A hex grid properly implemented is actually a 3-axis grid system that can be modeled as the surface of a cube. Trying to do it with a staggered 2x2 will result in all sots of hacky math issues.
    9
  47.  @jonas_badstuebner  I rewatched the original clip. The second guy accepts the statement that in-process concurrency is important, but in-process parallelism is unimportant specifically for web servers. The first guy didn't seem to know what he was trying to say and just agreed with the second guy. Anywho, I think they are still probably wrong with their implicit assertion that half-hyperthread Kunernetes pods were more scalable per dollar than larger servers with more resources. In the long term, it is cheaper and easier to scale vertically than horizontally, so why use a tech stack that guarantees you'll be unable to scale vertically if needed? Go's concurrency model is good in both scenarios afaik.
    9
  48. Sounds like they did not understand the concept of removing or updating something that turns out to be a problem.
    8
  49. Post-quantum crypto is lattice cryptography. Elliptic curves are theoretically vulnerable to quantum computers.
    8
  50. Would love to see an analysis of Python's garbage collection as well, if that is even possible. Iirc, the GC in Python runs at the end of every scope execution and removes anything that was referenced only in that scope (really, it uses reference counts and frees memory of anything that reaches a ref count of 0, but that typically happens at the end of a scope) -- I might be wrong or out of date with this.
    8