Comments by "TommyJ" (@ImperiumLibertas) on "Theo - t3․gg" channel.

  1. It's always comical when the "more than one way to solve a problem" argument is used to avoid having to learn a tool that is objectively more fit for the job.
    27
  2. Imao I was so lost reading "harder better faster stronger." I thought these were new elusive commands I was unaware of. You did forget bisect 😉
    23
  3. Theo is attacking the author of this article who he doesn't even know personally because of his subjective experiences. It's more like Theo is trying to win an argument by dismissing the author's points because of his "lack of experience" rather than on the merits. It's like he lost respect for the author because he disagreed with him and therefore it's okay to attack him personally.
    8
  4. Jack of all traits, master of none. Theo has a lot of surface level experience with a lot of languages.
    7
  5. He was emotional the majority of the video.
    4
  6.  @builtbywalsh  the original quote has nothing to do with the point I was making. Theo regularly proves that his technical knowledge outside of his silo is shallow yet he presents himself as very knowledgeable in many things. He's opinionated on things he has almost zero experience with. While being able to learn quickly is a great tool shallow knowledge is rarely beneficial.
    4
  7. Theo said it himself, he cant read this article in good faith. Everything he said was in bad faith and focused more on trashing on the author than actually attacking the merits of the authors post. "Instead of being on twitter maybe ship more shit" what a toxic and self righteous thing to say.
    2
  8. ​​ @ericgoldman7533 why didn't they know git? Did they lack industry experience? Not knowing git isn't the problem. The problem is not knowing a critical and fundamental industry standard tool of the trade that they should have been exposed to if they have any experience. Unless they're completely junior I expect them to know it and how to navigate with it.
    2
  9. I think server side rendering in general is a mistake. The majority of end user devices are very fast at rendering web pages. It leaves all of that compute power entirely unutilized. The last thing I want in my UI is for a backend change to cause a cascading affect throughout my application. In angular we separate out an api mapping layer specifically to handle server communication and map it to a front end contract so when a backend change is made only the mapper layer is affected the majority of the time. I don't want my UI to be exposed to backend complexity. Nothing to do with "separation of concerns." Instead we are isolating and segregating the complexity of the two applications.
    2
  10. ​​ @turculaurentiu91 for extremely agile teams developing extremely well defined products on strict timelines where maintainability isn't a concern and the engineers are going to develop full stack end to end having less defined layers may make sense since it can enable the team to move quicker. I'm thinking like a marketing promo site or one off tool for a contract. But that is an extreme minority of teams and products. Most teams are developing against rapidly chaining requirements that are not well defined with complex business logic. Separating each feature into its own API and allowing that data to be handled in a way that aligns with the business rules results in a very robust and flexible API. This prevents the way the UI is built or flows from influencing the way the data is stored or processed. One advantage of the latter is that the APIs become very usable on the frontend since they relatively inline where they are used. Even when using a segregated API strategy it is possible to write a data access layer and a UI data layer to write UI specific APIs and achieve all the same benefits all while keeping all the systems separate from each other. All of this comes down to one consideration, how impactful would a backend API change affect your ability to ship quickly. With a large and highly distributed app with multiple teams working on them keeping things separate makes sense. Apps with small agile teams that will own the code end to end a mixed strategy makes the most sense. tldr; big apps need more segregation between the data and UI. Smaller UIs with end to end teams do not.
    1
  11. ​ @PixelThorn my brother this is so unbelievably true. Product knowledge isn't a reason to hire an engineer.
    1
  12. Such an easy solution is to make all tag closings explicit. Whether its self closing or wrapping content all tags should be required to be closed otherwise assumed dangling and remain open.
    1
  13. I like const because it helps me identify places where my team or I are programming too imperatively and not using declarative or reactive patterns.
    1
  14. Take that analogy to the extreme with stacked diffs. The review comes down to the commit instead of the entire feature.
    1
  15. Git flow is terrible anyway. Don't use git flow
    1
  16. Theo, I've noticed a pattern in your videos. You attack people personally for asking genuine technical questions or when they ask for clarification. Its super toxic. Learn to separate yourself from the product and the outcome. Give people the benefit of the doubt.
    1
  17. ​​​ @no_name4796  hot take: using iseven is better than writing it yourself. Are you prepared to write and test all of the edge cases for iseven? What if iseven is passed null, undefined, "0", " asdf", NaN, [0], etc. Its better to use the dependency and pin it to a specific version and dont touch it unless you absolutely have to.
    1