🚫 Not Invented Here Syndrome 🚫

29 thoughts on “🚫 Not Invented Here Syndrome 🚫”

• poordome is not a pleasant motivator, it is an effective motivator

• Leftpad – use a package 😂

• CAN SOMEONE EXPLAIN WHY THE FUCK HE HIGHLIGHTS TEXT AND LEAVES OUT THE FIRST AND LAST LETTER IT'S DRIVING ME INSANE.

• And nobody listened. Nobody ever listens to the one guy in the room talking sense. I'm sorry Joel.

• 15:27 Infrastructure as code. You don't need UI. If you do, then you are a shitty programmer.

• Imagine using / complaining about AWS UI in 2024.

• NIHS is what created JDSL. Toms a genius

• …agen

• Another awesome video, Prime. You can pick basically any Joel Spolsky article and it's such timeless, insightful, wise piece of work. You'll never go wrong with Joel!

• This video is so anti-NIH that even the content isn't his.

• Flip is diabolical.

• 28:13 don't know how you got it twisted to mean that wealth is all that matters in achieving great things. There is an inherent advantage of being born wealthy. Your material conditions reflect on how you will perform in life. That's not a matter of opinion, it's a hard fact. It's awesome to know how you and people you know broke out of poverty by working smarter and harder. However, hat doesn't make it the general reality, just your experience.

• I hate using jquery, so I create my own ui library for every freelance project, every time i write it diferent from scratch!

• he left out one option between building it yourself and just using some package:
  Learning enough about existing software that your team can fix bugs and add features if needed.

  For example don't build your own wiki CMS, get regular MediaWiki and configure it, customize style sheets, add features via templates, lua scripts, addons and bots. And if necessary look in the PHP code to see the internal logic.

• Luck is when preparation meets opportunity.
  The better you are prepared, the less opportunities you need to capitalize (job interviews for example), and the higher your chances are to reach a 10%er opportunity.
  The more opportunities you are handed, the less prepared you have to be to capitalize on them (and the more 10%er you are obviously handed).
  In my mind that is basically the function of rich people having more opportunity and bad to decent preparation with lots of opportunities and poor people having less opportunities but way more preparation, as they need to be prepared for the few they are handed.

• I remember my second job after uni. I had to reimplantat an entire app from scratch for a device that already came with an app because one of the professors didn't want to depend on the company… He also didn't tell me what I was supposed to do until I started and I had to learn everything from scratch with no help to be found and I had 4 months to finish. 4 months of working half time, that is. It didn't go well.

  That kind of NIH isn't good.

  However, I remember several times when OpenBSD were not affected by security vulnerabilities because they did certain things themselves and made sure to make it secure. Guess it really depends on the situation if NIH is good or bad.

• "My daughter threw up on the floor" – looks like a memory leak, considered rewriting in Rust?

• C compilers were perfectly accessible in 2001. Visual Studio had been out for four years at that point, and its predecessor, Visual C++, had been out for a good six years before that. (I started using it around 1995 – about three years after I started programming in C at my first job.) Going all the way back to its roots, Microsoft C was first released in 1983.

• love this prime episode. Didnt expect you to go full life lesson mode at the end there and I 100% agree with all of it.

• The thing about Unreal Engine is that it perfectly exemplifies exactly what Joel is talking about.

  I thought UE5 was basically just going to be a big red "Easy Button" for making a game, but it really isn't that simple. Yeah, you can bang out a generic AF "game" using a lot of easy features and assets, but you can also directly write C++ code for pretty well any part of the engine and your own game. So, if 3D modelling isn't your game's selling point, but some really awesome new game game mechanics are, you can use and depend on other people's models/animations, rather than make your own, but completely invent your own underlying mechanics; or visa versa as well, where you can very easy make or get simple game logic/mechanics, but completely create your models and animations from scratch.

  EPIC is really knocking it out of the park with UE, and I think people could take a page from their book.

• That people are even using lodash these days shows just how many bad devs there are…

• Guys, I heard a rumor that this guy worked at Netflix before, is that true?

• We have our own ERP , Schedule-software, Time&Attendance-software, Backup Solution that integrates with a Proxmos+DRBD – Cluster solution we cobled into existance. We also have our own ticket system and a employee selfservice system.
  all systems integrate into the same Database…
  They were only meant to work for our company…but now we are selling them to our customers that allready have our Time&Attendance-software…
  the EPR was forced into existence by a customer that spend 500K Euros on a SAP solution that worked less good the the ERP that "we"(the bosses when they were university students) developed for them for MSDOS 6.2 . After the customer cried his heart out about how the world sucked we offered him to give us 200k Euros and he will get a new ERP that is tailored to his needs (it's a "big" single person owned jewellry design and production business). The funding was used to start the ERP that would fit our and their purposes and it was continually improved to be more of a general solution.
  My boss realy would have prefered to get the 500k they spent on SAP…lol
  We are kinda super cheap .

• I am working at a place that use a home rolled RTOS that is years beyond FreeRTOS.

  – Onboarding is more expensive since we need to explain so much more.
  – The RTOS is using a security model from the 90s.
  – The scheduler is ancient, clunky and rely on a circular linked list with 15k elements… On a good day.
  – The code base started in C, got switched over to C++, then back and forth with C and C++, leading to…
  – The code base is an unmaintainable mess. I'd call it garbage if it didn't actually still work.
  – The code base is so bad we actually use it as a deterrent ("either you do this or go work on the RTOS for three months")
  – Everyone hates the current situation but management refuses to let us upgrade the RTOS core since "it's working like clockwork and you are wasting valuable engineering hours" 😀

• 27:00 you have to be willing to lose something in the process of trying a bigger challenge. Not everyone can afford to risk what they have. Only privileged people can.

• Why do you not highlight the first and last letter of the sentence, when you highlight a sentence? Love your videos though

• I really don't like the term "reinventing the wheel" because there aren't any wheels in programming, you can't call electron a wheel, some times it's a good idea to make your own gui framework and build your app natively.

• My microloans service has six different logically grouped flows that do more or less the same thing, but they do them in slightly different ways and I felt like it'd be cleaner to just repeat myself six times with little variations than try to IF…ELSE IF…ELSE IF…ELSE IF…ELSE IF…ELSE IF…ELSE my way through it in one place.

• this comment is just for me to practice english.
  —
  people should feel ashamed by this.(1:58)
  i'm not dogging on clerk js.(3:40)
  they can be crazy expensive.(4:56)
  never roll your own off.(5:00)
  not invented here syndrome.(6:27)
  i'm not sure using webpack was the right choice.(7:45)
  why would you say such a jumble of words.(10:02)
  most people are on a mediocre team with mediocre programmers.(11:58)
  i am traumatized.(13:17)
  he scoffed at it.(18:06)

Comments are closed.