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

  1. More CoPilot code means MORE NEED FOR ENTRY LEVEL JOBS TO FIX UNMAINTAINABLE CODE PROBLEMS!! WOO!!
    61
  2. At least a few dollars/year from me... for one of the cheapest tiers of VM.
    12
  3.  @eduantech  It's not like Prime's point diverges too heavily away from Uncle Bob's. I would say he only lacks the compatible experience of writing TDD code or test cases in a way that he might find it hard to empathize or imagine certain "feelings" or judging things based on "smell/feel" as Bob describes. But the principles are quite close, especially with the thoughts on Agile. Though Prime has had a viewpoint against TDD and can't empathize with it much, I don't think it weighed down the discussion. Bob was well-spoken even when Prime was confused and did a good job of translating to topics/scenarios Prime could grasp and even agree with. I would argue that both Prime and Bob would arrive at a similar end point (if he isn't convinced already), just as Bob and his peers did in 2001. It is rooted in wisdom more than experience in a corporate/business world. I primarily think the direction that Prime's life has mostly influenced his little exposure and insight into TDD. If you give him years of the same kind of exposure I feel that the world would steer him towards TDD anyway. For the purposes of being a streamer full time I will contrastingly say that TDD is probably the LEAST entertaining topic, except for those who are truly passionate about writing test cases and working in such a way outside of a professional context. It doesn't make money, TDD has never been the thing that makes money on its own.
    7
  4.  @laden6675  no, he did a good job. he led bob to build his own arguments even when he disagrees with them. this comes from a person who is highly critical of prime in many instances.
    6
  5. Perhaps it wasn't considered due to the fact that majority of customers deploy on-prem?
    5
  6. Sometimes he also says things for views. Not that he doesn't actually disagree with the idea, but I'm more than sure he will come off as more opinionated than not
    5
  7. I agree. Prime definitely missed something. I would revisit his distinction between the two: CI is about "making sure your code is always working," and CD is about "making sure your code is always releasable." CD includes CI.
    4
  8. He probably omits PRs because he thinks pair programming is a better way to do code reviews (it might not work with open source), but it doesn't make any difference. If you find PRs prevent you from using this methodology, it probably points to an issue with the code review, not everything else. For your last question, it takes a lot of trust in your team; believe they will code using BDD/TDD and run unit tests before pushing. It is far faster to run something locally than remotely regarding unit tests. If your tests fail at integration (your integration tests), your unit tests are insufficient. Your design needs to be simplified, and you need to break it apart or have better interfaces with well-defined ways to speak to other components. The same needs to be considered for unit tests that run far too long. Suppose your unit testing is too simplistic to detect issues between things you might think are "external components" external to the module you worked on. In that case, your code needs better interfaces between the two systems. As for the rest of your questions, MANY resources cover these topics as the result of decades worth of software development. The XP book is an example of this, written decades ago. I tried to consider your question and any other questions you might have in this explanation. If something needs clarification, I will try to explain it my best. This is my understanding from looking at Dave Farley's videos on CD for the past two years and reading his CD book (although I admit I need to re-read it sometime soon.)
    4
  9. I would definitely like to see Prime pair up with Bob. It would set aside many differences and focus on the real meat of what it means to discuss software development
    4
  10. Right, a salesman that reluctantly brings up a book he doesn't think will even interest many people. Truly, the mark of an over-enthusiastic friendly salesman...
    4
  11. Most of all, he did not create many of these ideas. He just groups them together and re-explains what he learned from others. To talk to one another is to discover how little you know. It's a thoughtful direction for Prime to go into to bring such a guest on and dedicate an entire hour to. I truly think that his separation from the business world, like Netflix, has given him a clearer viewpoint on many matters as of late.
    3
  12. The exposure to general subjects to people who have become more mature, rather than in high school, seems like an overall well-rounded idea and a recipe to let people voluntarily retain more knowledge.
    3
  13. I expect writing a book is similar, based on what I've seen from some authors that livestream their book writing. Now, reading a book is much different. It is an experience, one meant to immerse and obscure the structure in order to make it least predictable. But, to write a book, I feel that some authors wrangle their own complex structure for writing by managing it in these sections/modules.
    3
  14. I totally agree with this. It is VERY easy to debate with him just from viewing this singular video, without any other context on what CI/CD is. It would help a lot of others who are confused to view his other videos, especially where he cites real-life businesses of various sizes with measurable success using CI/CD.
    3
  15. Also unfortunately, if you use it any specific use-case (especially one where a common design pattern in a common language isn't present) it hallucinates on every, single, prompt.
    3
  16. I don't know Bob's viewpoint on communism, but I certainly can see it as an insult to compare the work of engineers to what many Americans (especially older Americans) consider a failed ideology. A bit tasteless even in jest.
    2
  17. The Google mono repo goes against what you're saying about this may only apply to small products. He directly states in the video that CI does NOT only apply to web apps, as Vincent mistakenly mentioned in his post.
    2
  18.  @MyName-tb9oz  nope
    2
  19. If you're in meetings daily isn't it just waterfall? With these recurring meetings, it's just following a process...
    2
  20. @pnk4996 I'm confused on how you're disagreeing with OP. The LLM might have a different response based on the most common test case for your scenario, especially when the context of your prompt is niche and not in its training data. Test cases aren't for mimicking other people's tests. They're for writing design that you would use as if you were the end user, with an added side effect of having a way to track progress. It's text generation that's translated from a plain text prompt.
    2
  21. SOLID, Clean, any of these "scores" apply.
    2
  22.  @-Jason-L  And LLMs are terrible at TDD.
    2
  23.  @epiicSpooky  Agreed. And to some extent the hunting is an indicator that there's a poor design/missing coverage in the unit tests. If you start with integration test, you have the highest chance of writing a test case as close as possible to the user's intention.
    2
  24. Agreed. The other context is needed for prime. I thought I was stupid when I tried to dive into his videos two years ago! No... it just requires an open mind I think.
    2
  25.  @hm5236  You're right
    2
  26. I always thought it was contradictory that he rants against basic ideas like trunk-based development, CI / CD, clean code, and pair programming for a guy who preaches that the beginning struggle is an important phase when learning a new topic (which he himself admits that the struggle might be more commonly avoided when you rely on LLMs). I suppose one might overlook this contradiction if you only take his videos with a grain of salt and a pound of entertainment.
    1
  27. But what's the context of his quote? That matters a lot. He could EASILY be talking about his Java coding case study, where they might write production code before writing a unit test while doing TDD... As far as I know, CI/CD is a methodology for merging/delivering. Not strict rules, but guidelines perse.
    1
  28.  @HrHaakon  I think it's just a bunch of misnomers, but if you describe the behavior of the test double, the context makes it easy to find out whether it's a stub or a fully fledged mock object.
    1
  29. So you worked in a place that didn't trust you with access to the backend?
    1
  30. But the planning upfront thing he describes is more of a learning experience than generating an entire diagram describing a solution. Maybe it's an artifact from the UML days, but I think it's a bit heavy handed to call it "planning upfront" when it's more like describing a napkin sketch on a post-it note or a temporary drawing on a whiteboard. This is done less frequently and still consumes a very small amount of time compared to the actual time spent writing the code. I would say his explanation of it is a much more lightweight interpretation of planning, not meant to bog down the coder. The entire waterfall approach is in reality more reminiscent of heavy upfront planning because of having less access to frequent deployments.
    1
  31. New company, if you can.
    1
  32. I think creative writers are getting the largest bang for their buck with all this LLM business. If you write code as if you were a writer it could really create some creative ideas (even if they're completely wrong in the context of your codebase) and help you brainstorm as a result. It's a lot harder to mess up creative writing than code since it can be more subjective. That's not to say that LLMs don't regularly mess up writing stories by overusing cliches, having wonky plots, or nonsense/lifeless characters.
    1
  33. Primeagen Talking about supporting Agile Manifesto, not using LLMS?? Hot take: Well, not really a hot take, but I think Prime is revealing his true software engineer self now that he doesn't work in Netflix.
    1
  34. I'm honestly unsurprised Prime has quit Copilot. He is all about curiosity, but also staying on trendy trends. It's his job after all, especially so with him leaving Netflix. There are suggestions that LLM generated code is worse than junior level code. For the price, it's not worth it. Particularly when they start reducing/rate limiting responses and the quality of those responses.
    1
  35. Yes, I commonly hear the mis-categorization of agile to be a "noun," a thing to sell to project managers, rather than simply to be "clean" or "agile." It depends on how people interpret and sell it. Look at writing of the original authors and you will see it has soft points, few or no hard limits. It is meant to be vague. You could say it all equates to having "good manners", but that's not as catchy and sounds more parental. "Professional" sounds too corporate. It's hard to express things in English in a singular way to everybody.
    1
  36. Most definitely. you need to be able to speak in its language. I like to use it for exploring potential design patterns and interactions between design patterns.
    1
  37. I mean putting scams and influencers in the same sentence is a bit of a cruel joke when the video is based on pitching ideas as scams.
    1
  38. Most of all, you don't have automated testing. But you still can structure and re-read a book/newspaper article.
    1
  39. Isn't this the description of compulsions? Being compelled to enjoy something shorter but not a longer task like absorbing and reading an entire book? It's not new to social media. One might argue this isn't much of a phenomenon at all, we see it will adult videos/pornography.
    1
  40. 12:29 Regarding the interview techniques that are best for any given developer, I would argue there is no best technique. I've never owned a business so it might mean little, but I think it makes most sense to put your money where your mouth is. If you can afford to hire developers, you can take the risk of losing that money. And who's to say that once you hire somebody you can't fire them if they're not performing. It is always a risk to hire new developers because it can be so subjective and discriminatory in so many ways. Soft skills are probably the easiest to identify and are important. Save money by avoiding all these 'hoops' to jump through with arbitrary goals. Speed up the hiring process and speed up the delivery of the end product by hiring faster. That said, I think the bare minimum a hiring team should do is have budget for as many people they can hire for a single position, hire those people, and fire anyone that lied on their Resume AND can't deliver. Companies should stop hiring if they can't afford it, I don't think many companies can afford it in Q1/Q2 2024. A business trying to hedge their bets on the "one perfect guy" based on a crazy assorted system of screenings is rolling the dice. I'm not going to look favorably upon a team or company that encourages people to take needless risks. It's no different from a guy YOLOing his savings on a meme stock.
    1
  41. You don't need a mock object, but you easily could've written a Fake implementation of a database, like an in-memory database class, to accomplish this. That way, you can test the implementation of user validation and database operation without changing production code and then start writing new unit tests for new functionality. A mock would be overkill.
    1
  42. Say it with me, WATERFALL!!
    1
  43. I think the point of the "SOLID is for programming, not scripting" comment is there's a lot of external integrations in your example that you don't control nor want control over. It's different to follow when SOLID when you have to integrate with I/O a lot. Loosey goosey is a good way to go about it.
    1
  44.  @taliosnz  You still don't need a PR to help define a better contract that integrates with the code from another team. This can be done with pair programming still. If you work with the other team a lot, you may need to integrate more members between the two groups to get a wider breadth of knowledge. I'm not sure of my last statement, but I think it's more of an issue with team structure rather than code review structure.
    1
  45. Depends on the physics videos. If it's casual and in layman's terms, probably. But if you're watching lectures and exercising your mind along with the lectures that's irreplaceable and isn't easily done by LLMs. I'd argue doing fervent research is a lot different from fervently prompting an LLM for information/code which may or may not be hallucinated. I'd also argue researching with physics videos would supplement your ability to prompt AIs about physics questions in a way that's easily translatable to other physicists. Many things in moderation perhaps.
    1
  46. But simplicity is not always arrived to simply.
    1
  47. So this explains you don't necessarily need a mock object (or to an even larger extent, a mock library) to achieve testing. You can stub, fake, spy. Mock objects are usually much more involved (and nowadays generated by libraries using reflection). Again, mock objects are more involved because they're mimicking behavior of an actual API. They're really not necessary, that should just be an integration test. Just create a better design by abstracting away your external APIs and substitute them with smaller test doubles for unit testing. Unfortunately, as other comments mention, this makes a poor design where your test is tightly coupled to something still. So, if you're highly dependent on a certain protocol's response that overall indicates poor design and is an important portion of the code to minimize that impact.
    1
  48. 46:42 Locality of Behavior sounds like it is pretty different from separation of concerns, but I do not think they're totally exclusive. They're overlapping slightly in that both of these acronyms are ideas about organizing code. For example, you could group the markup, the scripting, and the styling for a button into one file (demonstrating a locality of behavior), this composes all the code involved in a single button while still providing a separation of concerns by keeping the different syntaxes together but separate from the code/style/markup of other elements in a different file. The developer may pick and choose over the other based on how they've grouped other portions of the code as well, but a consistency in choosing one over the other, or both together is important.
    1
  49. It's just a meme at this point. I dont think anyone claims he made that kind of a conclusion besides people that are just trying to purposefully bait people.
    1
  50. The examples in this video were absurd and inaccessible. You wouldn't use ChatGPT for domain-specific knowledge, it pushes for a more generalized answer with builder patterns. Though what it does indicate is your code doesn't follow any well-established patterns, which I would say is not a typical case for most people's code, especially in a language which relies heavily on typing. A lot of code patterns re-occur regularly. This is why I canceled my subscription from GPT 4 to GPT3. GPT 3 still has plenty of capability in detecting patterns, summarizing, but still has the same downsides of lacking specific knowledge, which is fine for $20 less.
    1
  51. People depend on it to write working code, but somehow manage to avoid the in-depth learning they could achieve from doing cursory searches on the topic they're working in. Great research tool to an extent if you can express yourself sufficiently in a single prompt.
    1
  52. I would say polite and maybe slightly intimidated. I think it might be intimidating to see Bob laugh so frequently and intentionally during some of the arguments. But, maybe, he's just trying to make it feel less serious and more open to discussion with that. Whereas Prime is taking it a bit more serious because he's trying to purposefully understand. The ending was extremely awkward though, I got a laugh out of it.
    1
  53. So HTMX simply extends the abstraction of what an anchor, a button and a form can do and generalizing it to other elements through HTMX attributes? It seems like a unique way to extend the declarative nature of HTML and really supports the original idea of HTML. I'm unsurprised that such a useful abstraction hasn't been done until now, I'm more surprised at some of the neat functionality that presents itself just from this concept (the lazy loading, active search, etc.)
    1
  54. If it's a niche bug that requires context, it will be terrible for that. But if it's a bug based on a flawed design pattern, it might do well in pointing that kind of bug out.
    1
  55.  @krYrrr  I'm a lay person when it comes to these kinds of situations, but I agree. I don't think anything productive is being done here except the lady is wasting the company time by asking questions when they're declining to answer all questions. Probably the only way to get an outcome is through a court.
    1
  56.  @krYrrr  I wonder the same thing, depends on perspective. If she has savings, it's probably not that big of a deal. For HR people, I already feel the stress of just dealing with HR people from an interview perspective, I can't imagine what it must feel like from a firing perspective from their end. I suppose some people can thrive in a small world, but I find it hard to see that HR people don't feel conflicted that their imprint on the world regularly involves the suffering of other people for the sake of appeasing some faceless corporate entity that doesn't care for any single person. The company has a red flag of wasting of finances on these absurd processes. The tech isn't exactly bleeding edge, there are competitors, and so it's nothing to sacrifice your own personal life to. The corporate leaders that initiated this entire controversy are still in place. I'm speaking from my anecdote of being a late joiner to a public company that finally met an "end of the line" from a long history of mass firings (restructurings), only keeping the top 1% who were "long tenure" employees that were members of the original (overly large behemoth company) that went through repetitions in history experiencing companies hirings/mergers/firings. One particular event involving significant financial/tax fraud, and a final nail in the coffin due to bankruptcy. Anyway, my anecdote goes to show corporate KPIs/metrics really mean nothing, except for their finances perhaps. The common tie-in between these companies that constantly restructured was the finances. Hiring software guys is expensive, keeping your software running is expensive, some software is just not worth it.
    1
  57. I loved my software engineering class. It SUPER briefly talked about SCRUM for maybe half an hour in one lecture and then we started our own software engineering project w/ 3 other teammates. We would spend maybe only 5 min on SCRUM everyday and I was totally fine with only investing 5 minutes. I loved how we went over assertions, unit testing, and we even went over agile manifesto & design patterns from a high-level all in one class. That was the most value I've ever gotten out of a CS course, perhaps because I'm more interested in developing applications compared to traditional Computer Science.
    1
  58. CI is included as part of CD...
    1