4 ms·
It’s kind of risky to have programmers who feel so passionately opinionated about the software that should power a business. It’s doubly tricky, because most c
by sillysaurusx 7y ago
It’s kind of risky to have programmers who feel so passionately opinionated about the software that should power a business.
It’s doubly tricky, because most companies pay lip service to passion. But like a chef that cares a bit too much about which cookware you use, it sometimes hinders the goal of serving 100 customers at noon.
I respect that they’ve created their entire networking stack from the ground up. Few can claim the same. But objectively, the less eyeballs on a piece of code, the more risk. What will the company do if they’re hit by a bus?
I’m not sure that companies should be measured in terms of “what if a dev suddenly goes away,” since creative work isn’t interchangeable like gears in a machine (nor would we want it to be). But it seems at least partly relevant.
The tradeoff is that if you use unpopular software, like lisp, you can often gain more leverage in specific situations. HN’s software is the most flexible codebase I’ve ever seen, but few have ever studied it deeply. Viaweb used those principles to dominate the competition at a time when everybody was writing websites in C. But are those days gone?
It might be an asset for a startup to use obscure software, so it’s definitely worth honing the skillset. I’m just not sure it’s a good idea to feel so strongly about business in particular. It has a way of burning you.
- zelly 7y ago> The tradeoff is that if you use unpopular software, like lisp, you can often gain more leverage in specific situations. HN’s software is the most flexible codebase I’ve ever seen, but few have ever studied it deeply. Viaweb used those principles to dominate the competition at a time when everybody was writing websites in C. But are those days gone? In Paul Graham's days, Lisp was not as unpopular as it is today. It was more like choosing to use Ruby in 2020. On its way out but still in the public consciousness.
- sillysaurusx 7y agoHmm. I think Viaweb was the first web application (or at least, no one's disputed that claim) and they kept their choice to use lisp a secret until acquisition. If someone else was using lisp to make websites, it seems like they must have independently rediscovered the idea. It was started in 1995 and acquired in 1998, so that wasn't a very long time for lisp to come into the public consciousness. It seems like at best it was considered an AI research language.
- zelly 7y agoNo one was making web applications with anything. The consumer-facing web was still in its infancy. > It was started in 1995 and acquired in 1998, so that wasn't a very long time for lisp to come into the public consciousness Lisp was the only game in town other than C for multiple decades. Absolutely everyone learned it in university. It was the main garbage collected scripting language, like Python today.
- pjmlp 7y agoDuring the 80's and 90's that place belongs to Basic dialects, not Lisp. And when Viaweb came to be, there was also ML, Smalltalk, Perl and Tcl to choose from. This if we focus only on the context of UNIX, because otherwise the language spectrum gets even wider.
- p_l 7y agoViaweb started a year after complex web applications were done, including White House information system using COMLINK system built on CL-HTTP (designed at Intelligent Information Infrastructure Project at MIT AI Lab). I think I've also seen GUI apps exported over HTTP using clickable image maps and early tricks for streaming images. Viaweb was one of the first "make your own shop" web applications, yes. Not first web application.
- p_l 7y agoAs for Lisp - in computing circles, it was very big name, at least in places that weren't on the low-end side. The Second AI Winter was at the time heavily kicking it by association, and big name companies had just went under (Symbolics, TI shuttering Explorer line, etc.)
- csharptwdec19 7y agoLISP won't die until Autodesk says so. Seriously, the AutoCAD community has some of the brightest (or, at least, most clever) developers I've ever met.
- ludamad 7y agoIt is indeed risky to give people with non-business allegiances product ownership - and as you say, it is all too tempting to lean into such passion. However, I believe the author has an infectious drive that I find an intangible benefit that outweighs the intangible downsides
- tw04 7y agoThat’s a potential issue for a startup. Joyent was acquired by Samsung. They could literally hire 100 top tier devs to shadow him with the money they dropped between the couch cushions. Getting hit by a bus wasn’t ever going to be an issue if it was ever a concern.
- ludamad 7y agoYet they aren't doing that, they are laying people off. When you need to reduce personnel, losing out on an information silo is definitely a concern
- p_l 7y agoThat's on the people doing reduction though. There should be an active policy of reduction information siloing that is active all the time, especially for a big corporation like that.
- tedunangst 7y agoHow many of Joyent's struggles relate to having their own network stack?
- RantyDave 7y agoNone. I think. Not being Linux is a bigger problem.
- smacktoward 7y ago> like a chef that cares a bit too much about which cookware you use, it sometimes hinders the goal of serving 100 customers at noon. It puts me in mind of a line from the movie Gettysburg (https://www.imdb.com/title/tt0107007/?ref_=tt_ch https://www.imdb.com/title/tt0107007/?ref_=tt_ch). Robert E. Lee, explaining his decision to make a risky attack to one of his lieutenants, says “to be a good soldier, you must love the army. To be a good commander, you must be willing to order the death of the thing you love.” A business built around a particularly clever bit of code faces the same dilemma. To be a good programmer, you must love that code. But to be a good businessperson, you must be willing to order the death of the thing you love.
- crimsonalucard 7y agoTo be the best business man is to do good business without compromising your ethics. Aim to be the best.
- elcritch 7y ago> It’s kind of risky to have programmers who feel so passionately opinionated about the software that should power a business. While you have a point in general, I don't think that was a primary reason for Joyent losing the "cloud wars". At the most you can say is that passionate engineering doesn't always lead to commercial success. > I respect that they’ve created their entire networking stack from the ground up. Few can claim the same. But objectively, the less eyeballs on a piece of code, the more risk. What will the company do if they’re hit by a bus? AFAICT, they didn't write their own network stack from the ground up but based it on OpenSolaris and many of the devs were former Sun employees. That's far from "write you own network stack". Joyent started in 2004, when Linux didn't have DTrace, containers, and likely didn't compare in networking performance, so it would've made a lot of sense to run a cloud startup on an OpenSolaris base. They also shared drivers and network code with IllumOS and other OpenSolaris forks. Not exactly a bus factor of 1. Joyent was one of the first container companies, which were based on OpenSolaris Zones, but seem to have just missed the "Docker" container wave. That and Joyent never quite hit on the same developer-oriented Docker CLI and Dockerfiles otherwise, who knows what would have happened. I still think of Zones as superior to Linux namcespaces/conainter setup in many aspects, much less back in the early 2012-2014 when containers were just becoming "a thing". Nowadays it's mute with AWS's Firecracker and CPU support for virtualization there's essentially no performance penalty for VM's like back in 2012.
- pjmlp 7y agoActually IBM and Unisys were the first container companies. The last couple of decades mainstream OSes have been catching up with mainframe world.
- nicholassmith 7y ago> It’s doubly tricky, because most companies pay lip service to passion. But like a chef that cares a bit too much about which cookware you use, it sometimes hinders the goal of serving 100 customers at noon. Chefs that care deeply about cookware will either go one of two ways, flame out or Michelin star. It's a hugely risky strategy but the pay off from staffing a business with people who care incredibly deeply is potentially very high as long as they're well managed. Early days Apple is probably one of the best examples of it, but Microsoft is probably the excellent counterpoint to that as well.
- dasil003 7y agoAs one of the first customers of Joyent (aka TextDrive) in 2004 who funded the company via a prepaid "lifetime" hosting account, I think you hit the nail on the head. The CTO was in love with Solaris, constantly waxing poetic in the forums about the next great technical idea he was implementing while the shared hosting we had prepaid for suffered constant downtime and technical problems. While I think they eventually sort of got their shit together (just based on outward appearances, they had long since burnt their bridge with me personally), it's really no surprise that they lacked the customer-centricity to succeed in the cloud wars.