4 ms·
I believe the article has a wrong take on this, and it seems more like a rant to generate views than an actual analysis of why people write things that already
by warkanlock 4y ago
I believe the article has a wrong take on this, and it seems more like a rant to generate views than an actual analysis of why people write things that already exist in the wild
It's not about spending time but considering all the actual real learning of making a complex piece of software (maybe if you focus too many dev cycles into it might become harmful). Still, at the end of the day, you will have a team of almost experts in X topic who can go back and even improve on what they are doing (using any other common, well-known framework)
And yes, I agreed with the author that it doesn't make sense to write one just for the sake of it, but as Feymann said: "What I cannot create, I don't understand."
- doctor_eval 4y agoI think there’s a big difference between building something to learn about it, vs accidentally building something complex in order to support the thing you’re actually trying to build. The point is, just use a database. We’re talking 15 minutes of effort. Or to paraphrase someone wiser than me, 4 weeks of programming can save 15 minutes of installing.
- pictur 4y agoWelcome to the world of today's tech gurus. These guys are busy sharing what's wrong and what's right on Twitter all day. The number of people who talk about real world applications is almost non-existent.
- swyx 4y agofor what its worth i was just writing a database complement to https://rachitnigam.com/post/you-have-built-a-compiler/ https://rachitnigam.com/post/you-have-built-a-compiler/ because i thought the format was really helpful in understanding why we independently evolve the same things from first principles. i’ve done some of these mistakes in real life, but adding anecdotes would have spoiled this particular story format.