6 ms·
A lot of shaking off of weak developers. I don't say that to insult the very talented developers during that time who couldn't stay employed. Rather, they suffe
by bdcravens 12y ago
A lot of shaking off of weak developers. I don't say that to insult the very talented developers during that time who couldn't stay employed. Rather, they suffered along with the rest, due to way too much supply. Developers who knew one language who could get hired merely by having a word or two on their resume and having a pulse; when things dried up, everyone who should have been an entry level sales person were all clammering to get the jobs and money they were used to, but it was a buyer's market at that point.
You made it through by being versatile. Not by starting to learn while you were job hunting, but being prepared when jobs were aplenty.
You had to be ready to be employed in a non-VC funded world, doing boring things.
I liken it to today, where you have an abundance of 6-week boot camps and developers writing code against the sexy Javascript framework du jour. Those developers will starve if we hit another period where VC dries up.
Learn some boring stuff, even stuff that gets laughed at on HN. .NET. Java. In places like Houston, there's TONS of jobs, but they're not in Rails or Clojure or Angular. They're in .NET, writing apps for big oil or healthcare.
Though it wasn't as big then, I think learning dev-ops will really take someone far when no one's writing Twitter aggregators or social networks for quadcopters.
tl;dr When times are lean, boring languages in boring companies that make real, not VC, money is how you stay afloat
- deleted 12y ago[deleted]
- deleted 12y ago[deleted]
- axotty 12y agoHistory is bound to repeat itself... What you say almost makes me want to learn enterprise.
- bdcravens 12y agoI think it's best to know what you love, but also know what has massive demand. And by demand, I mean outside of the startup bubble. If you're lucky, you'll never have to do enterprise, but I'll be damned if I tie my ability to feed my family to a philosophy. :-)
- unclebucknasty 12y ago>What you say almost makes me want to learn enterprise. Perspective is a funny thing. I started in the enterprise and was there through the bubble (excluding a brief stint at a startup). I then went on to found my own company some years later. Anyway, it somehow never occured to me that people actually depend upon the startup ecosystem continuing to thrive, and would feel absent options without it. I mean, I guess it's obvious, but I suppose I just hadn't consciously considered that it really implies "startups as a career". So, it's somewhat hilarious for me to read someone musing that maybe they should "learn enterprise". I'm also not in SV or another startup hub. So, I'm sure it's partly cultural as well.
- axotty 12y ago> it's somewhat hilarious for me to read someone musing that maybe they should "learn enterprise". I'm actually still in school. So, I tend to muse over learning a lot of different things. Your life story was really neat though ;)
- unclebucknasty 12y agoInteresting. I wasn't aware there was a choice between "learning enterprise" and (other?) in school nowadays. Back in my day, you'd come out with a solid foundation, equipped to make those choices. Hey, another perspective thing. Fancy that! But, I'd say, yeah...get you some "enterprise" while you're there, especially if they're offering it for the same price. ;) Glad you enjoyed my life story. Happy to share.
- axotty 12y ago> I wasn't aware there was a choice between "learning enterprise" I never said that. The GP was specifically talking about enterprise Java and .NET, which was what I meant. I guess I was being overly terse, I apologize. My phrasing seems to have bothered you. Doctors recommend people your age nap frequently to avoid these kinds of passive aggressive mood swings. You'll be just fine in the morning. Good luck!
- cmdkeen 12y agoPatio11 made a very good point in one of his posts that enterprise, specifically Japanese enterprise, taught him a lot about engineering skills. There's an entirely different philosophy out there from the startup "push code to production on your first day". That of (lowercase) solid engineering practices where production releases are major events that require lots of interactions, checks and planning. It teaches you an awful lot. Safety critical industries, and many financial companies after Knight Capital, are good places to learn this kind of discipline.
- Ologn 12y agoI agree. I went from dot-com Unix admin to investment bank Unix admin in 2000. Luckily it was via a consulting company. They said my interview process was unusual, because every internal interviewer passed on me, while every interviewer from a dot-com gave me a strong recommend. I was interviewed by them many, many times and finally accepted. It was very different. At the dot-com's that I was at, web servers and application servers were Red Hat Linux, and only the databases were Sun boxes, with E4500 being a high end box. At a post-IPO dot-com there might be one E6500 and maybe a few Sun E4500's, and lots of Red Hat machines. At the investment bank they were all Solaris on the Unix side, and had dozens of E6500's in my city, and hundreds of E4500's. The investment bank had admins in the OpenBoot PROM all the time, whereas I had barely been in it. The investment bank was always replacing disks in the hundreds of external RAID arrays they had whereas only our database had a large external RAID array. They used NFS extensively and you had to know it thoroughly. My knowledge about Red Hat Linux, Apache web servers, Java application servers etc. didn't amount to much. It was qualitatively (and quantitatively) very different, and in interviews it sounded like I didn't know what I was talking about. On the developer side, the bureaucracy is very different. If a minor change in a software package is being pushed to New York, London and Tokyo, which often it is, you might have five meetings about it, and the code push might take weeks or even months. No matter how trivial the change. Three different divisions might have to sign off on the change. It's definitely not an agile code process, with code going from your fingers to the production web/app within the week.
- kokey 12y agoUnix admin here too. I also spent more time with Linux and FreeBSD during the dotcom era, but, strangely, for a lot of enterprise companies because I was working more on the security side of things. When I had to cast my net wider after the bubble burst, and after having moved to a new country, my lack of deep enterprise Solaris experience did bite me. Fortunately after a few years Red Hat was starting to do really well in the enterprise market and I ended up in banking, where I picked up a bit of Solaris again but I didn't really bother too much since the bank was actively getting rid of Solaris. I suspect many technologies used in the startup world now will get taken on in the enterprise after the bubble burst, but it will certainly take a few years and these companies will be weary of people who doesn't have enterprise experience.
- kokey 12y agoI used to say that the bubble bursting got the people who quickly got themselves an MCSE so they can 'work in IT' and get paid well while they have no IT skills, to go back to the jobs they should have been doing like sales. That's what happened, and many of them then ended up as estate agents.
- john2x 12y agoWould iOS/Android be considered enterprise today?
- mtrimpe 12y agoNo; unless you're building iOS/Android-based workflow apps for supporting factory workers e.a.
- 0942v8653 12y agoMost "enterprise" things are mainly server-side and the mobile clients are just CRUD interfaces, so yes, some of it would be considered enterprise, but only the really boring stuff.
- balladeer 12y agoTo be honest, calling Java and .NET boring and laughing at these is just a hipster's indulgence.
- Jgrubb 12y agoOr a smokescreen to keep the market balanced more in their favor...
- raverbashing 12y agoBut at the same time, if you need to go through tons of red tape (either from bureaucracy/processes or even tools) to change something simple this is a big demotivator (at least for me) Last job involved C# and it was good, and dynamic (pun intended)
- collyw 12y agoJava was the coolest / most hyped up language back in 2000. Was .NET even around then?
- bdcravens 12y agoNo, it originated in 2002, but the equivalent was VB, COM, and ASP. That said, I was speaking in the present tense.
- turnip1979 12y agoIn 2000 proper, the crazy hip thing in the Java world was J2EE. Seriously ... being proficient in Enterprise and Session beans got one a 100K+ job back when that was a big thing.
- netcan 12y agoTo strengthen your point, by the mid-2000s there was a booming industry of well paid "consultants" developing software for the public sector, big companies and such. Largely .NET. It wasn't sexy. A project could be deploying an intranet and making it play with some other stuff. There weren't stock options. People wore suits. The pay was certainly not poverty level and the required skillset was pretty achievable.
- einhverfr 12y agoNot just weak developers though. I don't have a CS degree, so I took one look at the job market and realized my only option was self-employment because I would never get past resume screeners.
- bdcravens 12y agoFor what it's worth, neither do I. I did get my first "real" job in 2000, in the midst of the madness, but since then, my lack of education credentials has been an issue maybe once or twice. But +1 on self-employment, I think that's a more fulfilling path.