4 ms·
If you think home-rolling a solution is the answer
- jqpabc123 3y agoYears ago, I home rolled my own web server. Why? Security --- it is dedicated and limited to a single purpose so every request can be scrutinized and validated and verified. Attack surface is minimized and totally unique so any hacker is starting from ground zero. The only common vulnerability is the OS network stack. After 25 years of being openly exposed and attacked on the internet, it has never been breached --- at least to my knowledge. In that time, I think I've saved a lot of time and money watching exploits for commonly used web servers just pass me by.
- Shawnj2 3y agoThis is a good point (at a small scale until you become large enough to be a target people spend significant time targeting)
- jqpabc123 3y agoPeople target my server every single day. They mostly try off the shelf attacks geared toward known vulnerabilities and common misconfigurations of popular web servers and setups. And these don't work --- so they mostly give up after a while.
- Shawnj2 3y agoBecause those are more likely to yield results than trying to figure out how to break your custom web server. If a big company suddenly started using it or AWS made your custom web server a default option then that would be a different scenario.
- birdyrooster 3y agoFrosgren comes off like a newb, because they equate home-rolling with downtime and being embarrassed explaining to your customer what you do. When I home-roll I have less downtime usually than relying on a vendor solution. But I have been doing this a very long time so maybe it is an unfair comparison; of course, I’m not so gauche that I am prefixing Dr in front of my name on Twitter.
- mooreds 3y ago> Frosgren seems like a newb She co-authored Accelerate: https://www.amazon.com/Accelerate-Software-Performing-Technology-Organizations/dp/1942788339 https://www.amazon.com/Accelerate-Software-Performing-Techno... . She is also currently at Microsoft Research and was previously at Google and GitHub. This may be a hot take you disagree with, but she's no newbie. I took her point to be "make sure anything you build is a lot better than anything you can buy, because there are a lot of unexpected expenses in building".
- deleted 3y ago[deleted]
- birdyrooster 3y agoCo-author means they could have been carried. I have worked at those companies and they were not meritocracies. I’ll add “if you are inexperienced” to that quote and agree wholeheartedly.
- mooreds 3y agoHow about being the lead author on all these papers? https://nicolefv.com/research https://nicolefv.com/research I haven't read any of them, nor done a google scholar search to see how many were cited, but it sure looks impressive to me. > I’ll add “if you are inexperienced” to that quote and agree wholeheartedly. 100% agree that experience matters and can teach you when to ignore rules of thumb such as "prefer buying to building." But I've seen experienced developers succumb to the siren call of building their own, say, database pool, when they should not have.
- Pannoniae 3y agoThis is really reminding me of a cargo cult. I observe that there is a prevailing mindset among software engineers that their peers are always better than them, and if there is a "standard" solution, it will always be better, more performant, easier to use, bugfree, etc. compared to a quick home-rolled version. This is a good thing if you want to contribute to software bloat, but most use-cases can be solved by rolling your own, then adding features as needed. I have a specific example - I wanted to do logging in a program I made. I experimented with adding different loggers to the project but all of them were more complex and harder to set up than what was needed. Ultimately, I've written a logger which does exactly what I need and in the exact same way in a few hours. (the standard loggers needed some finicking to produce output in the format I wanted)
- mooreds 3y ago> it will always be better, more performant, easier to use, bugfree, etc. compared to a quick home-rolled version. You're leaving out crucial time factors: * which is quicker to market * which has the lower maintenance burden Buying, in my experience, wins on those axes. It does, though, depend on the size of the problem, which is a good callout. You rolled your own logger for a known format. You didn't roll your own RDBMS. Also, you experimented with other solutions to determine if they were feasible. That's exactly the kind of experimentation we should all do--survey the problem space before jumping into building something. I daresay you prove the tweet's point. For your problem, your solution was way better than the other options.
- Pannoniae 3y agoYou are right in the fact that for complex systems, it will always be quicker to use an off-the-shelf solution than making your own. However, for maintainability, the most important metric is the raw amount of code, followed by the engineers' abilities and the code's level of documentedness. So, if you can replicate what you need with a third of the code, you are already in a much better position (and can fix your own code quicker than a third party's!) than if you had to wait for the vendor/a poor guy reviewing your pull request.
- 3y ago
- torstenvl 3y agoI think home-rolling is almost always the answer, unless: - The IRL subject matter is distinct from your core business, programmatically distinct from your core in-house software, and generally the same across businesses (accounting, HR, etc.); or - The product is open standard or otherwise highly interoperable, and has a permissive license (e.g., zlib, sqlite); or - The product is highly complex and hard to get right (e.g., encryption, etc.). In cases affecting your core product, with expensive licenses, and it's pretty easy to get it right, owning the software/platform outright clearly wins over incurring massive perpetual overhead just to make devs' lives possibly easier.