HNHacker News
TopNewBestAskShowJobs

elbrodeur

899 karma · joined June 17, 2010

Designer & Front end developer
submissionscomments
elbrodeur··on IPhone 4
"Ford's new engine is incredibly powerful and well designed, but it's missing a low gear setting on the shifter." Might be more apt.

Again, Neue is leaps and bounds ahead of regular old Helvetica. It's a total bonehead move to leave out italics even though most people won't notice it's absence.

elbrodeur··on IPhone 4
As a designer, Helvetica Neue (even without italics) is a huge step in the right aesthetic direction. His original point was not so much about the font, but about the platform. He lays the groundwork, showing that the platform was higher resolution and therefore it made more sense for a font that displayed better at higher resolutions to be used.

I think it's a valid point and a great critique -- how is it contradictory to praise what is praiseworthy and point out what is wrong?

elbrodeur··on IPhone 4
It's a positive, thorough review by someone who develops on the Apple platform. Do you comment on Silverlight developers glowing posts as well? Or do you just dislike it when Apple developers do it?
elbrodeur··on R.I.P. Chatroulette, 2009-2010
My feeling is that the increased prevalence of single-sign-on services like facebook connect, OpenID, google connect, etc. will help to mitigate baddies and pervs -- if you're putting your reputation on the line, anonymity is decreased. People will still make dummy accounts, but if single-sign-on is coupled with a karmic or whuffie type system it will be another tool to identify and discourage trolls.

Granted, we're a long ways away, but we're getting there.

elbrodeur··on 60 Days at a Startup
The point on the company's team is the most salient, I think. If this is your first startup, making sure you're a good fit for them and they're a good fit for you is really important. Consider a couple of the reasons people join startups:

1) To learn. If you join a company with bad founders, poor communication or inexperienced members you can still learn, but there are barriers to learning that are unnecessary.

2) To have a significant stake in something new. If your team does not value you, it's easy to get discouraged and stop caring about the product or to feel marginalized and worker-beeish: If you wanted to build something for someone else, why not just work for a more established company?

3) To build work experience. If you don't fit with the team or the team sucks, it's going to be really hard to put on your resume for your next venture/application.

In short, at an early stage startup, your place on the team can literally make or break the product. If you guys work well together, the product will fail or succeed on it's own merits; if you don't work well together it can doom the company.

Be smart.

elbrodeur··on 60 Days at a Startup
This is a question is sort of a chicken/egg problem. By the time you're ready to be a co-founder you usually are one or have been one before.

It's like being a parent, really: Reading every parenting book on the planet, getting a degree in Child Development and attending lamaze classes won't make you a good parent. Being a good parent will make you a good parent.

By all means strive; but by the time you're ready you'll probably find months or years of being a cofounder behind you.

elbrodeur··on Ask HN: Can startup founders afford to spend time on "hobbies"?
DO NOT UNDER ANY CIRCUMSTANCES GIVE UP THE THINGS THAT MAKE YOU HAPPY

Your work may bring you satisfaction, joy and the desire to work long hours; but that ebbs and flows. Some weeks you'll be so excited to be eating ramen noodles and building something that is distinctly yours, the next you may be stressed out about the fact that you haven't figured out how to monetize.

This is why it's important to recharge -- even if you don't think you need it.

Me? I like backpacking. We were bootstrapped for 6 months before closing serious angel money and once a month I left friday night and came back sunday evening. Once a month I couldn't work on the weekend. And even though it was expensive at the time, it made me sane and filled up my gas tanks for a month.

Working 12-14 hour days is fine as long as you do something that makes you happy and refuels you when you need it. If 1 hour a day is what you need, it's an extremely small price to pay for peace of mind. Additionally, my bet is that you'll actually perform better at work.

elbrodeur··on Mike Lee on why he can charge $1,000/hr for iPhone development
Interesting approach to customer acquisition. After taxes he'd be sitting on just over a million a year without working much more than 40 hours a week.

But maybe his pricing is predicated on the desire to not work 40 hour weeks?

elbrodeur··on Pi is Wrong
I use UNIX time. So there.
elbrodeur··on Why aren’t Apple's error messages written by marketers?
Defensive Design by 37 Signals and Don't Make Me Think by Steve Krug are both great books about how to design for when things go wrong. Engineers, in addition to designers, should read these books post-haste. EDIT: If you're a hacker in SOMA/SF and want to borrow either of these books they're very quick reads.

The trouble with technical error messages is that almost invariably, engineers end up writing them. "Not my area of expertise" or "I put in a request for copy months ago" are some of the many reasons that poor error handling happens.

Additionally, having a truly helpful environment requires additional resources: In the example in this article, the "Heres how to fix your problem!" link would require an additional application to keep track of known issues and solutions.

That being said, it's exactly how every application should work: Error messages like this may not be daunting to more technically proficient users, but the vast majority of users are not technically proficient and many users simply give up (if they can) when they see an error message that they are unable to understand/fix.

elbrodeur··on Ask HN: Typical Startup or Abuse?
Damn. After reading your post and the comments I want to emphasize a few things:

- You are being screwed. This has been amply covered. - You are worth your weight in gold. If you really work 10 hours a day, hang out with your family then work into the late night... you are every CTO/VP of Engineering's wet dream. - You have rights. The law, in many places, is built to protect people like you from exploitative situations like this. Just looking at a glance, it seems like you could - if you so chose - bring this guy to court and walk away with a more equitable amount of compensation [INTERNET CAVEAT MACHINE ALERT: I am not a lawyer and this is not legal advice.] - You deserve better. With your work ethic and your attitude I hope the next group of people you work with give you your dues

elbrodeur··on Questions to Ask When Interviewing at a Startup
I don't think it's a matter of proving anything. I think the issue is that no matter what the answers to these questions are, you have a good reason for interviewing the person.

"What past success and experience do the founders have?"

"Well, we've been involved in small projects individually like a b and c. But we've surrounded ourselves by great advisors like Mr. W who did x in 2001. And Mr. Y who was CTO at Z Corp."

etc.

elbrodeur··on Questions to Ask When Interviewing at a Startup
The chances of you seeing a section of code that is central to their IP and the answer to the question, "how did they do it?" and, additionally, your ability to instantly understand it are very slim.

This is a great question for an engineer to ask. Being able to see if the code is smart (e.g. using shorthand instead of multiline logic), neat and documented is a great way to get a feel for how your potential future coworkers work. They've spent the last two to four hours grilling you and know you, how you code and how you solve problems pretty intimately -- why not get to know them better, too?

elbrodeur··on Questions to Ask When Interviewing at a Startup
This list of questions is great. I would say that some of these are a bit invasive as you pointed out, but a good sign that the applicant is really considering the company. I think casting aside someone who is genuinely interested in the future of the company would be a silly move: Even if you're not transparent about your financial situation, you should at least be honest about their chances of having a job in 6 months.
elbrodeur··on Ask HN: How do you cope up with the emotional rollercoaster of a start up?
There's no real answer to this question. Here are some things that might help:

1) Separate your work from your life. Even if you work 12-14 hours a day, have something you do that is away from a computer and distinct from work. Work from home? Set up an office area and leave the house at the end of the day. I like going for long walks.

2) Get a hobby. Something that doesn't demand too much time but is engrossing. I like to read fiction. Currently reading Spook City by William Gibson. Psuedo-sequel to Pattern Recognition. It's decent. Reading can be, if you let it, a micro vacation.

3) Exercise. It helps with anxiety, depression and fatigue.

4) Know that this is not the end of the road. You have to try your hardest to make this work, but if it doesn't it's not a big deal. It's not going to ruin you. Or be a mark against you on your resume. It's going to be the best thing to have ever happened to you, success or no: Learning from your mistakes is an option. Success is an option. Failure is not.

/techpep talk

Also, some other perspectives: http://www.youtube.com/watch?v=2CdJTfGiRCI http://www.youtube.com/watch?v=TROhlThs9qY

elbrodeur··on Ask HN: Why won't start-ups hire older, experienced programmers?
I think this is a huge part of it. As you get older you naturally acquire and subsequently have to maintain things -- they can be material (a mortgage, car payments, insurance, etc), emotional (dog that needs walking, kids that need feeding, wife that needs attention) or other obligations. And that's just obligations. There are other reasons why startups fail to convince older, more mature and more experienced developers/engineers.

Kids fresh out of college are easy to convince for little or no money and the slim chance of glory. As you get older you are more realistic: Even if this company is successful it won't make me rich. Even if the technology is awesome to work on it may not make the company successful.

We tried really hard to grab a couple of really brilliant engineers right after we closed our angel round. The reality? While what we were working on was cool, they could make twice as much as we could afford to pay until we closed our Series A and even though our options package was decent, it wasn't generous enough to make them rich even if we had a generous buyout or IPO (which, you know, who knows if that will ever happen). Plus it takes 4 years to vest.

← PreviousPage 5 of 5