HNHacker News
TopNewBestAskShowJobs

zalambar

93 karma · joined November 7, 2011

I build things.
submissionscomments
zalambar··on Makerbot announces new 3D printer: Replicator 2
Look at it another way. Here we have a process which may not be much of a barrier to customers who consider the product a major purchase but is apparently chasing away potential buyers who are prepared to spend several thousand dollars on an impulse purchase.

That's an unfortunate filter to have in place.

zalambar··on Faster Fourier transform among world’s most important emerging technology
No problem, just find a way to implement the algorithm which doesn't violate at least one of at least 121 "fast fourier transform" pattents and you're all set (http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sec...). Just repeat that process for every algorithm you might want to implement and you'll have no problem writing software.
zalambar··on Engineer rigs nerf gun to shoot himself when his stories are rejected in Pivotal
That's neat but it seems counter productive to me. I consider rejected Tracker stories to be a good thing. Better for a story to be rejected and provide feedback than to sit ignored or remain unfinished longer than necessary because the developer wants to avoid any possibility of rejection.

Now firing nerf weapons when CI builds fail makes much more sense.

zalambar··on PUT or POST: The REST of the Story
My mobile client is consuming your API over a lossy and high latency network. Some of my requests will time out. Sometimes I will drop offline after sending a request and not be able to receive the response. Which requests can I retry safely?
zalambar··on Does My Rails App Need a Service Layer?
Jared suggests using services to translate into different protocols. I see a further use for services to translate models into different representations on the same protocol in order to support a versions API. Let a service handle mapping outdated API payloads to the latest version of the domain model.
zalambar··on Hiring Employee #1
I am a contractor and part of a larger consulting shop so I'm biased but I have to agree with ahoyhere. You get a reliable burn rate which is adjustable on a schedule you can negotiate. If you're hiring a team of contractors you should get a group who have proven that they have an effective and efficient process for working together which they can apply from day 1 and you can probably scale the size of the team based on your needs and budget. When your needs change or you pivot and you need an expert in a new technology which I don't know I'm happy to walk away or swap places with one of my peers who may be a better fit. I'm also fortunate enough to have coworkers lining up future projects so neither you nor I need to worry about what I'm going to do if you no longer need me or just need to slow down development an focus your resources elsewhere. I'm certainly not invested in your startup the same way an employee might be. I'm not going to work crazy hours and I'm not going to pull off long shot programmer heroics (well not unless that's what you ask for). Instead I can measure my success only by the quality of the work I produce and the value I can deliver to you immediately. Building the tools you need to validate a product-market fit or get a MVP in front of users is often my end goal, not an incremental step towards hopefully seeing a return on some equity share. If I'm lucky I'm helping a startup build a new product every couple of months. I think that offers a breadth of experience which relatively few prospective full time hires can match.

Startups will need employees and employees invested in and committed to their long term success. So while your looking for the perfect first employee, the one who has the combination of personality, skills, passion, and mindset you need, consider if the right contractors might let you get a lot done in the mean time.

zalambar··on New York vs San Francisco in fight for tech start-ups
When I see these location discussions I'm always curious how much of an impact non-compete clauses play in starting or recruiting for a startup.

California has "16600. Except as provided in this chapter, every contract by which anyone is restrained from engaging in a lawful profession, trade, or business of any kind is to that extent void." and without such employee protection in place I would be very nervous about trying to start a company which might compete with a former employeer. Similarly it seems hard enough to find talented designers and developers already without having to consider that the individuals with the most relevant experience might be barred from completing with their current employers.

zalambar··on LHC May Have Found Crack in Modern Physics
"LHC does exactly what it was built to do".
zalambar··on Generating realistic-looking stories in Pivotal Tracker
I see Tracker as a prioritization tool first and a way to capture stories second. It is highly opinionated about and focused on prioritization but leaves the details of story writing and the conversations apolzon is looking for up to you.

I like this balance and aim for brief story titles with descriptions which include the "As a <role>, I want <goal/desire> so that <benefit>" style requirements, implementation concerns, and other acceptance criteria. I could certainly see a place for a more opinionated story writing tool though. Especially for team who struggle to produce actionable stories.

I also see a Tracker story as a placeholder for a conversation which needs to happen. Not as a good tool for mediating that conversation in the story comments and attachments.

← PreviousPage 2 of 2