Comments by "Edward Cullen" (@edwardcullen1739) on "ThePrimeTime" channel.

  1. Booo! YouTube is no fun, won't let me post anything remotely risqué 😭
    2
  2. How in the hell did you get that conclusion? I'm sorry, but you're failing to understand just how OSS works. They are abusing trademark - they are claiming the use of WordPress, exploiting the technicality of OSS without engaging with the spirit of OSS. You say this is "punishing WordPress users" how, exactly? The user contracts are with WPEngine and WPEngine is a $$$ company, versus the volunteers who do the work of keeping it going? Either your understanding or your moral compass are messed-up, either way, the copyright and trademark holders have the right to do what they want, within the bounds of the law.
    2
  3. You misspelt "anyone" as "normies" 🤷‍♂️😁
    2
  4. I am vindicated in my view that JS is trash. I should feel happy. I am not.
    2
  5. "Typescript was a mistake." When you finally realise that you've been polishing a turd.
    2
  6.  @ra2enjoyer708  Given this is what I do, I'm going to vehemently disagree. It is not the tool that is the problem, per se (though NPM solves the wrong problems), but the entire ecosystem and how it is used/managed. Python (pip) ecosystem is not even close to being as bad, though, the influx of data scientists and AI researchers in recent years has degraded quality overall. Turing Completeness is nothing to do with this problem - I question whether you actually know what you're talking about.
    1
  7. Yeah, except we already know Vector > Linked List.
    1
  8.  @samjohns8381  If you know what the code should do, you can describe the test. If you don't/can't, your requirements are not described sufficiently, so what you're doing is requirements discovery/elaboration. What and how are totally different things. You just don't think of it this way, because you were not trained properly (this isn't a slight, just an autistic statement of fact; very few people are taught properly). I'm not sure Dave says so explicitly, but to me, this is actually the key benefit of BDD/TDD. Done right, you cannot write any code - waste any time - if you don't have your requirement nailed down. This doesn't mean full waterfall, it means that you understand what you're trying to achieve with the code you're about to write. It should make you also answer difficult questions ahead of time, such as "how do I handle errors", something in my experience, people tend to leave until it's a problem... But when it's a problem... I'm a fan of "document first", because this makes you think about how people will use the code. Which should help stop you from writing hard to use APIs.
    1
  9. ​ @scythazz  LOL. Agreed. Java is awful.
    1
  10. The best comparison is not tennis, it's touch-typing.
    1
  11. CIA No, not that one, the OTHER CIA... 😊
    1
  12. 😂😂😂
    1
  13. I was told the same thing 20 years go 🤷‍♂️
    1
  14. "It failed in an unexpected way." This is a requirements/specification issue, not a code problem. The point of TDD is that you're working to fulfill a requirement. If you don't know what your requirements are, you're buggered anyway... My feeling is that a lot of what we do is figuring out what the requirements are as we're coding, which is necessary sometimes, but also feels like a bad habit. Stable code and stable requirements are two entirely separate issues - I wouldn't even call them orthogonal because they are so different. I've been spending a lot of time investigating TDD and I think that the main issue is that it forces honing in on requirements and testing first, which is the completely opposite to how most people learn/are taught how to code.
    1
  15. LOL, okay, so I wrote this about halfway through watching and made exactly the same arguments Dave did 😂
    1
  16. Good conversation and conclusions.
    1
  17. ​ @titfortat4405  I'm 99% it wasn't about his insecurities, or even the insecurities of the OP... But then, I don't go about living my insecurities through my 'programming language of choice' (only my failures and regrets)...
    1
  18. ​ @basilefff  Gotos in error handling are only required for poorly structured code, or code that adheres to arbitrary "don't use nested if statement" nonsense, which is every bit as cancerous as goto itself. Goto only remains valid in extremely performance critical code, which 99% of people never need to write - and half of the 1% definitely shouldn't!
    1
  19. Important point, badly made. Better take: Knowledge is temporary, understanding is permenant. Mindlessly following a tutorial will only ever increase knowledge. Engaging with a good (which are rare) tutorial will build knowledge and understanding. To reallly grow, you need to test and reinforce your understanding by going beyond the tutorial. Always focus on understanding. ChatGPT is bad for exactly this reason: it discourages understanding, so you will be stuck as soon as it doesn't compile or doesn't do exactly what you need.
    1
  20.  @Selendeki  Yeah, well, I dunno, maybe I've been doing a Masters (after 10 years in industry) and had exactly this interaction with some undergrads? Just maybe. Mature Devs who are looking for a leg-up on getting started with a new library or whatever, well, that's something else, but why you'd think that I had these people in mind when I wrote what I wrote... Well... I'm sorry for not being excruciatingly explicit in every single word and concept I was trying to express, in spite of the context (the video) rendering it unnecessary, well, except for the extremely insecure, I guess. 🤷‍♂️🤦‍♂️
    1
  21. It's when you're forced to use something that is awful, that's what gets people, me especially. Ruby works, but is fundamentally awful. List.foreach()? List.fuckoff().
    1
  22.  @sack-shaw  Study(s). Don't have the citation to hand.
    1
  23.  @bobbyn946  "Perfectionism" is, itself, a symptom, but is also used as a pejorative, in place of "won't do exactly what I tell them and I don't understand why". In software, "perfectionism" is almost indistinguishable from "being good"; a computer program is either correct, or it isn't. A person who is not conscientious simply doesn't care about how they are performing; they do not care whether they are performing at the right level to justify their position. This should not be confused with "being a fraudsters and being anxious about getting caught"; imposter syndrome only applies to people who genuinely earned a position, but don't feel they do. Fraud is something completely different.
    1
  24. Trollope is another word for "Lady of the Night." Can't believe bo one picked up on this...
    1
  25. I hate to say this, but there is a serious skill issue here. The author does not understand the distinction between the System Call (SysCall) Interface and the wrapper library that most people typically use to access it. The Linux SysCall Interface is defined by the kernel implementation. For convenience, C implementations usually provide a wrapper around this, because setting-up and managing the result of a SysCall is a PitA. There is absolutely nothing stopping the Rust community from implementing their own SysCall wrapper - they just haven't done the work. This would need to be done once for each OS (with some variations based on CPU arch). Yes, this is a mammoth task, especially for Windows, but it is what it is. If you want your own native SysCall wrapper, then you need to do the work. "Annoying" on Linux/Unix systems, nightmarish on Windows, yes... But you can always try to persuade MS to do some of the work...
    1
  26. Understand that this was completely unnecessary and entirely the fault of Kier Starmer. You're welcome, I guess... 🤷‍♂️
    1
  27.  @timseguine2  Hmm... I guess I need to dive into the Rust docs to get the full picture, but this still doesn't answer my question... There all sorts of (ba)sh escaping and interpretation issues that could be exploited to result in arbitrary code execution. My issue is that passing untrusted arguments to any shell process is, definitionally, suicidal and no one seems to be talking about this. It's like saying "pulling the trigger while pointing a gun at yourself is bad", when we should be saying "you shouldn't be pointing a gun at yourself, full stop!"
    1
  28.  @rusi6219  Dunno if my full reply is delayed, or I tripped the bots, but, in short, invoking a shell with user-supplied input, is always a gun. Calling a .bat file is invoking a shell, as would calling a .sh. Believing any runtime (Rust, C, whatever) can make it not a gun is a mistake; they are, at best, a trigger guard.
    1
  29.  @timseguine2  Agreed. The main issue is "user supplied input". Constraining this is incredibly difficult, unless you have a very strict grammar (for the non-programmers, this means you have a very limited list of valid inputs that you can check against). Even designing a grammar is hard, as it's surprisingly easy to create one that is ambiguous (flashbacks to Compiler Engineering at Uni 😅). And that is assuming that you set out to formally create a grammar, as opposed to accidentally manifesting one as you develop your product! 😂
    1
  30.  @joseoncrack  They have, to an extent - there is PowerShell - but Microsoft will not break backwards compatibility. As I imply, this is more a developer problem than a Microsoft problem... I have reverse-engineered and re-implemented many .bat files to avoid this kind of problem. But doing this requires time, patience and a deep understanding of "no matter how long it takes, it's better than the alternative." 😅😂
    1
  31. You only hate stored procedures, until you're working for a large company with 30+ years of database evolution where many different teams are doing raw table access... And it is your job to modify said tables. I worked with an experienced dev who worked for 2 massive UK retailers - his wisdom on this was undeniable and has stuck with me. He absolutely required all DB access via stored proc. As to business logic in DB layer, this is a guideline, not a rule. One that you should try really, really hard to stick to, but if the alternative is to slurp gigs of data across the network to get megabytes of useful results...
    1
  32. Wish I'd been involved in this when it happened. I strongly empathise with so much of this. What I have come to realise is that so many of the problems are due to lack of appropriate training/support. It takes practice to learn to say "no" and there are many ways to say "no". I have seen many 35-40 year olds (around the age they start having kids?) "checking out" of the profession, doing contract work for the day-rate and simply not caring anymore. My view is that we older, more experienced people, need to take responsibility for fixing the profession. In my experience, there is very little respect for developers in the workplace. This is what we need to change. The average, competent-to-good programmer, temperamentally, will be vulnerable to falling in to bad habits. This temperament needs to be "countered" by a strict training regimen - think about the way doctors are trained to "be" doctors.
    1
  33.  @an0nsaiko890  No, the author focused on syscalls, because "the only way" to access them is via C libraries. Any other library can simply be re-implemented in Rust.
    1
  34.  @an0nsaiko890  You need to re-read what I wrote and the other replies I've made in this thread and comments section. According to the article author, "the only way" to access syscalls is via C function calls. Your response is really quite embarrassing.
    1
  35. I'm "pro-exceptions" and I think this is a truly awful argument for exceptions. 🤷‍♂️
    1
  36. ​ @i_dont_want_a_handle  Oversimplification. No one really cares about criminal justice reform. Far easier to virtue signal about starving children in Africa and refugees from wars half-way around the world.
    1
  37. The long+short being, that you must review the code yourself and not "leave it to someone else".
    1
  38. ​ @emptystuff1593  No. Power BI is designed to connect to databases.
    1
  39. I'm so BORED of people playing this constant pissing contest of language "performance". It's just dumb and people making it never work in truly high-performance enviroments.
    1
  40. ​ @hannessteffenhagen61  This.
    1
  41. The best analogy is the Kia USB vulnerability. If someone went around stealing and crashing Kias to "bring attention to the issue", they are still doing something malicious and hurting innocent people who did nothing more than buy a Kia in good faith. Saying "the people who stole the cars did nothing wrong, it's all Kia's fault" is utterly retarded.
    1
  42. "Study", you mean "survey"? Yeah, basic methodology: surveys suck and are least reproducible.
    1
  43. Nit-picking reviews is an uber low-T move. Just stop it.
    1
  44. On your closing comment about the EU/Brussels... NOW you're getting Brexit.
    1