But I think you probably need an app in the store(s) long term, even if it's a wrapped web app.
1,614 karma · joined June 3, 2013
But I think you probably need an app in the store(s) long term, even if it's a wrapped web app.
But, a fresh exec or management track engineer? You could make a difference and climb the ladder.
It depends on where you are. Different folks need different opportunities.
I know what I’m doing. Been at it for years. It works for everybody. There are so many people who deserve a shot but will never get one, if you’re willing to dig and develop there is no shortage.
The answer is not and will never be writing bigger checks with money you don’t have. It’s getting real up close and personal with your team and figuring out a way for everybody to win. If folks want to ride my ride, that’s super, but most cats don’t really have a taste for my risk and work profile. Where I excel is professional development and lifestyle. I can move the needle for people there.
The option is available to all, but very few take it. For really good reasons.
“Where’s will?” “I don’t know, our manifesto says nobody gets to know when he’s working.” “Well he broke the site.” “That’s his right as a sovereign citizen.” The end.
Furthermore, the odds of the leaks continuing approach certainty at this point. Even in a civil trial, who would perjure themselves over a job? (Pleading the fifth is a potential option even in a civil case, but is real problematic and probably will make a criminal investigation even more likely.)
The only time to do something important is right now. If you found the person you want to spend the rest of your life with, marry them. Today. Life won’t wait.
Secondly, the culture of startup Uber alles is real dubious and I question the wisdom of dedicating yourself 100% without question to a group of venture capitalists who are, bluntly, counting on most of you to fail. Trust is reciprocal. Don’t get too far out over your skis- this is business and managing resources and risk is your job. I’ve been doing this long enough to know that you are costantly triaging your time and energy, and without a strong sense of priorities and boundaries, you will be totally consumed by the endless cycle of other people’s wants. There are a lot of people who will tell you to go all in and sacrifice everything for the company. I think most of those people have an agenda that is serving their interests over yours.
Lastly, man, I work real hard and have for a long time. You have a ceiling where your hours are going to get real soft efficiency wise on a consistent basis. You can go 60 hours a week with a family. Very few people can put more than that number of hours in at their job without experiencing a real sharp productivity dip in their per hour output. I would submit that most of the folks going 80, 100, 120 a week for sustained periods of time are getting nothing they couldn’t have with a disciplined, 100% focused schedule and a family. They’re selling out the only life they’ve got for a handful of sloppy meetings or ugly code. Go home and have dinner with your kids. Hug your husband. Get a couple hours in on the weekend. Delegate more stuff, better. Focus on finding and executing what’s going to move the needle, and cut out the rest.
Yeah, you're right, if shit isn't shipping, it's my fault.
But.
There are a variety of psychological profiles in computing, and they have various pluses and minuses. I need folks with kind of a... move fast and break things attitude. That's what I select for.
Furthermore, the 80/20 rule is a super real thing and the last 1% until a project ships hurts real, real, real bad. There are people who can push through that and there are people who can't. Yeah, it's my fault we're not sipping tea as we ship, but I've been doing this a long time and I'm pretty good at it, and I can't make that pain stop. I just can't. I've been on teams that shipped and suffered, and I've been on teams that didn't ship.
If somebody's cracked this code for me, man, throw me a bone. But while I'm always trying to do better, I also kind of have given up. I'll make it up to you on the other side, I promise, but it's gonna hurt a little pushing it out.
There are hordes of false negatives in any hiring process, anyplace. My process is more accurate IMHO but it’s indisputably more work and it does not scale at all. Ultimately everybody is going to beef with any criteria they don’t align well with and I have to remain flexible enough to not throw the baby out with the bath water. I don’t mind getting drug a little on HN— I have a good team, and their open source contributions might not be as impressive as you assume.
Honestly the code review isn’t for the obvious rock stars. Anybody can pick them out. It’s for the sleepers who might not get a fair shake but who can deliver.
Believe it or not, there’s next to nothing I’ve ever seen that was the remotest bit interesting on an industrial espionage level. Just regular old business logic that was either cleanly done, or not.
I honestly could not recall any of the crap from the interviews I’ve done beyond a sense of how people thought.
Anyways, you wanna do some interviews your way, be my guest. I will happily send the guys who don’t want to do show and tell to you. I’m not trying to be all things to all people. No open source, no closed source, no side projects? We can play API bingo or code a b-tree, but prob not a culture fit.
It’s much more cost effective to invest in your existing people. That’s one thing I never skimp on.
But if you didn’t, for whatever reason, and you happen to have an illegal copy of some production CRUD app hanging around so I can look at how you organize your thoughts, nobody I’ve interviewed has ever gotten even a whiff of heat for letting me look over their shoulder and see how they wrote their schema. I don’t want a digital copy and I could give a shit about your illegally retained IP (and there’s a whole lot of it floating around). I want to know what you name your variables.
The best way forward is absolutely some open source code, folks clean up better in public and you don’t have to make apologies for things that weren’t your fault.
But this smells like folks just wanting me to take their word, and it ain’t gonna happen. I’m flexible, but when in doubt I choose ‘no’. If the next guy can prove it and you can’t, hey, plenty of fish in the sea.
Whiteboard stuff selects for a particular algorithmic dexterity that I just don’t need a lot of the time. And rejects some of the grungier virtues that make a big difference in moving units in production.
Hiring folks for a couple weeks is fantastically expensive in management overhead. I gotta be highly confident you will work out to take that step.
Just hiring a bunch of dudes and firing the duds is similarly expensive and I frankly don’t want to be that guy. I hate firing people just because I was lazy interviewing. This is my job and I take it seriously.
And there are a whole lot of guys that just don’t ship. They show up. They commit code. They are prompt and attentive at meetings. But if you need to ship, they just can’t shit it out. So many organizations are rotten with these guys- you wonder how so many devs can produce so little product, this is the reason. (Also shitty management- mgmt is ten times noisier and a hundred times more expensive if you fuck up.)
I don’t really disagree with your philosophy of working while you’re working and NOT working in your downtime. I think the same way.
But I have a whole pile of stuff I can show you that I’ve worked on. I don’t ask anybody to take my word for it. In computing, you just can’t. The signal to noise ratio is too bad, there are too many guys out there making unmaintainable junk, if they actually ship anything at all. There are shops out there that can afford to hire a bunch of maybes and just weed out the duds when they wash out, but I don’t have that luxury. Nor am I going to go on some weeks long hiring safari where I hire you for a week or two and see if you can cut it. No time man. Sorry, don’t have it. I’m going to give you the job or I’m not going to give you the job.
It's far from easy to bootstrap, but you basically solve all the problems these guys are talking about if you can survive it. The problem, of course, is that your unit economics have to work, you have to have the personal patience and resources to get to profitability, and you have to survive a potential funded competitor using their financial leverage to sell at or near a loss and torch your position in the market.
So a lot of folks take the money, but you take the money, you gotta pay it back. An IPO is ultimately just kicking the can down the road, and taking on a new set of guys that are going to cash out your venture debt for public debt. Who also expect to be paid back. I don't see a way out of this devil's bargain short of, you know, delivering on the milestones you talked about in your pitch deck, or in your roadshow.
But spare me the crocodile tears, huh? You took the money, you gotta pay back the money. Plus interest. And a lot of these IPOs, they had to make big promises when they went public-- big multiples, big projections, to support big valuations. Now you are sitting on a big pile of teachers' pension money and you have to deliver.