Hacker Newsnew | past | comments | ask | show | jobs | submit | sobes's commentslogin

Author here.

That's a great use case where a quantifiable improvement would lend itself to a business case as an approximate ROI calculation could be made.

I will have to think of how to extend the functionality of the model to support this. Perhaps using the existing behaviour as "road segments", then having the "arrival sequence" of one segment originate from the cars exited from another segment.

Thanks for your comment!


As someone who's worked as a Software Developer in Toronto for the past 13+ years, I totally disagree with this assessment.

First off, very few very early stage startups expect you to work for free until you get funded. Exceptions being that you're a co-founder or an unpaid intern that never touches code.

Secondly, while the startups in Toronto are probably less well funded than the ones in the US, not all require you to work for 12+ hours a day while paying you for 8 hours. It looks really shady to set these expectations especially since we have clear laws around overtime pay in Canada (describing such a work situation to friends will raise eyebrows -- definitely not the standard practice, whatever industry you work at).

Lastly, I'd say that any place worth working at (big or small) will be insanely picky about who they hire. Current employer included.

All of the above are from personal first hand experience. Of course I haven't worked for every single tech company in Toronto but I have worked for several (mainly early stage startups).


> First off, very few very early stage startups expect you to work for free until you get funded. Exceptions being that you're a co-founder or an unpaid intern that never touches code.

Obviously this is not something I have a lot of statistically accurate data for but, me and my friends are recent graduates and collectively have applied to quite a lot of very early stage startups in Toronto and out of those, we all have experienced the bait and switch of unpaid work till funding at least 50% of the time.

> Secondly, while the startups in Toronto are probably less well funded than the ones in the US, not all require you to work for 12+ hours a day while paying you for 8 hours. It looks really shady to set these expectations especially since we have clear laws around overtime pay in Canada (describing such a work situation to friends will raise eyebrows -- definitely not the standard practice, whatever industry you work at).

I didn't say all startups are like what I've mentioned. The one I'm currently working at is awesome! That said, it's more often the case that startups use their short runaway as an excuse to make you work long hours (and just to be clear - the 12hr / day was not an estimation - I was literally asked my thoughts about it during an interview - that company is still recruiting on HN Who's hiring for more employees and a quick google search shows they have increased headcount to 35 people this year and is profitable).

> Lastly, I'd say that any place worth working at (big or small) will be insanely picky about who they hire. Current employer included.

I have 0 problems with employers being picky. I worked closely with the CEO of a previous startup and I totally understand that. What I don't understand is the point of claiming you need to hire a developer (with a start date of immediately) and then leaving the position open for months altogether, or having crappy working conditions.

BTW I've interviewed at Nulogy (if that's where you are currently working) - Since this is a throwaway I can't give too much details, While I was still disappointed for the reason I was rejected it was one of the good interviews I've had (interviewer was knowledgeable, I learnt about the company and product, the tech stack, the problems they were facing, what was expected of me, and just some personal chit-chat during the coffee walk).


Nulogy.


Can confirm, I work there. Fun and hardworking company with a strong growth culture.


We also have/use:

- TDD

- pair programming

- git flow

- a 2-week release cycle

- four dev teams


I'm talking about all financial institutions being non-profits. Financial institutions would not have a responsibility to shareholders to show a return on investment. Instead they would only have a responsibility to provide a needed service to society (i.e. the creation of and access to capital).


"The recovery operations were challenging," Musk told reporters from Washington, D.C.. The seas were heavy, he said, so the recovery team suspects the stage was destroyed. They were, however, able to find pieces that join the first and second stage.

If they were able to recover the stage from the ocean, it would probably take about a couple months to refurbish it for flight, Musk said.

Source: http://www.businessinsider.com/elon-musk-will-make-an-import...


Find a company that:

1. Isn't a "startup" anymore (by Steven Blank's definition of the term).

2. That's been founded by engineers (you might a better cultural fit).

3. That still has a fairly small workforce (so that your contributions still feel significant enough for you).

4. That's profitable, and self-funded (no pressure from investors who don't understand what the business is trying to do, only understand that they need to see +10x returns)

How carefully have you been choosing your jobs? I don't think you're being too demanding. However, you are being unrealistic if you're not vetting the startups that you're applying to.

That's just two cents from a dev who's been working at startups for the past 10+ years.


> The cure seems worse than the disease, in my opinion.

Totally agree with you on that.

Given that the idea of usernames (originally called handles) predates the internet (http://en.wikipedia.org/wiki/Citizens_band_radio), I seriously doubt the practice is going away anytime soon.


Just because you find a passion, doesn't mean you have to spend money on it. There are an insane amount of free learning resources online (in tech/dev, which I'm assuming what your pro background is). Similarly, I'm seeing an increasing number of bootstrapped startups (they just don't make as much noise as the funded ones).

My twenties were about realizing and coming to terms with the fact that there are people who are smarter, more clever, and more knowledgeable than me. My thirties are about figuring out how to work with these people as much as possible. I do feel that I'm late to the game on this. If I got over my ego earlier and/or had a more collaborative mindset I'd be in a better spot.

Keep looking for that passion. But don't do it alone. Once you find it, it'll be with a group of people "better" than you to help you figure out what to do with it. :)


Is there ever a reason / use case in JS to NOT use the strict comparison operators (=== and !==)? Browser support? Performance? Logic tricks?


Only one that I can think of, and a frequent one:

  if (a == null) bla;
This checks for null and undefined.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: