danielvinson

1-2 sprints, which for most teams is 4-6 weeks. It really depends on use cases... generally startups don't have any need to support old browsers and can enforce current Chrome+Firefox only.

As a frontend dev, this really pains me. I’ve worked at many places with the same problems - first of all, pushing back on the designer is incredibly important if something is hard to develop. Most designers are doing their best to make things easy to code, but aren’t developers, so they just don’t know. It’s the engineers job to tell them no when things are exceptionally difficult. If they understand that the style change they want is a 3 month project, maybe they would be happy to design something different.

Secondly, frontend is hard. Having a senior react dev who can accurately weigh the trade offs of using external components like that would have been invaluable here. People underestimate how much different in skill level a junior react/frontend dev is from a senior engineer with experience in multiple frameworks. 6 months is long time in terms of dev hours - writing a table from scratch for your use case that works with design is usually a 1-2 sprint task, and that’s absolutely the hardest one there. But more reasonably, work should have been done to make a reusable style library to make this even easier.

I tried this out and I really just need a way to manually set the latency. My recording computer only has an audio interface with no monitors (just headphones) and I pretty much can't use this software because you don't seem to support ASIO input or manual latency settings.

It really depends what type of candidate you are looking for and what sort of job it is. One of the often overlooked roles of a hiring manager is understanding the signals coming in from the interviewers, weighing the results properly against other information, and making sure that the interviews actually gave information which can correlate to on the job performance.

In the past when I've been the hiring manager, I've had inexperienced interviewers ask my candidates questions like this for all kinds of positions - when you look at who does well in other interviews and gets an offer (and performs well), it basically never correlated at all to performance in whiteboard-only CS-focused interviews.

In this case I was interviewing for a full-stack senior position where there would almost certainly be zero systems-level coding, so the interview should have been a throwaway at best.

In this case, it played out as a wrote it - I offered some solutions to the problem and thought about different ways to solve it, then implemented the one I thought was best on the whiteboard. About halfway through he asked me why I wasn't implementing the best version, so I thought some more about it and couldn't come up with an in-place solution (which is very hard to find in an interview setting), so I continued down the same line when he wouldn't give me any help. After the interview his feedback to the manager (which I received because this was through a referral) was that he expected me to have this algorithm memorized and he gave me a "Strong No Hire" because I couldn't give the best solution.

Its worth noting that I received offers from over 50% of companies I interviewed at and I certainly am not bad at coding - this was just a particularly bad interviewer using a very bad problem. With this company, I actually told them I wouldn't accept an offer even if they did give me one because the interview was so bad.

I’m a college dropout and have about 8 years of experience as a developer. I’ve been interviewing a lot lately at mostly startups (7 onsites in the last month). Every single place except for one asked me about college or why I dropped out. One place asked me incredibly difficult whiteboard problems which appeared to be to filter out people without CS degrees (very specific algorithms to implement which I’ve never heard of before). One place had me reverse a linked list on a whiteboard, and was rude and standoffish when I commented that I’d never thought about doing that before so I didn’t have the algorithm memorized.

The job I accepted is the one job that didn’t even mention my lack of a degree and gave me practical coding problems.

Happiness isn’t just a factor of compensation, it’s also if people enjoy what they are working on, how they work, and the people around them.

I agree with this concern - one of the most common complaints I hear from my friends and coworkers is that they keep getting extra responsibility handed to them, but never actually see the promotion. There is an incredibly delicate balance between motivating people to take on new challenges and discouraging people by not giving them enough in return for it.

The best way to handle this situation (for the employee) is to just sidestep the problem and offer the increased salary and promotion upfront with the new responsibility. There is the additional benefit of internal visibility - if somebody is taking on extra responsibility, it is able to be communicated to the whole team, dodging the common issue that engineers face of not knowing who in their organization they should go to for help/mentorship.

In general, I think people would appreciate the link not being to a paywall.

Yes, this is being overlooked by most readers... this article is a woman plainly describing her mental illness.

If somebody wants to work for me and really, honestly, cares if our tech stack is new and fancy (as opposed to practical/easy to maintain/easy to hire for), that is a HUGE red flag that they are going to leave after a few years or suggest major technology changes that are not in the best interest of the company.

> From my understanding though they're just a wrapper API around the car manufactures existing apis?

Yep, think EasyPost for car functions

This chart is absolutely beautiful, great job! Is this made using pure D3?

IANAL, but this is exactly how B2B sales works... you offer an absurdly high MSRP then offer discounts with various incentives based on completely arbitrary things, with the average purchase landing nowhere near MSRP.

I'd be careful about pricing this way to consumers since states are now started to see pricing differences as discrimination. See: http://nymag.com/intelligencer/2018/02/tinder-prices-discrim...

I'm a former competitive MtG player. My playgroup found that with a bit of practice and a specific technique, we could roll 17+ on any spindown dice almost every time (try rolling the die with it starting in your hand with the 20 facing upwards with a sideways motion). While technically you can use any method you choose to randomly determine the start of a game, these dice have been proven to not be "random" thus cannot be used in a tournament. It doesn't matter at all in casual play, but in a tournament, you're just giving your opponent a chance to play first for free.

I think the correlation they were getting at is - both are mental health conditions and both have a high rate of recovery during patients' early 20s.

While I agree with you that the correlation here doesn't have any direct relation to addiction based on the evidence provided (a study connecting ADD/ADHD to addiction would be VERY interesting), I think that the author included it to show that not all mental health conditions have a low recovery rate.

I feel like this is just a very short-sighted view of the JavaScript ecosystem. A huge amount of JavaScript applications aren't used internationally, aren't used on mobile, or simply aren't websites. I've worked on multiple projects that are served locally from a pre-downloaded package (for example a Kiosk UI).

I really don't understand this... while yes, I might at some point be interested in reducing my bundle size, for 99% of developers out there, a difference in 300kb is just completely irrelevant.

I choose my JS libraries because they are actively maintained, have well designed APIs (easy to use), are common enough to where newly hired developers already know them, and just generally make my life easier. This doesn't address any of that.

All of these seem like the exact ideas every executive thinks sound great then get shut down by literally everyone else... would higher user engagement even increase conversion rates? Probably the opposite. Mobile support? Nope, just alienating mobile users with a worse experience.

How is that better than a debit card?

My company did something very similar when we had a customer make a large order shipped overseas, which turned out to be with a stolen credit card. They didn't realize that since our hardware requires a service plan to even operate, we could just put a note in our system that these were stolen and inform everyone that tried to use them that they had purchased stolen goods and that they should return it (and report stolen goods on eBay).

I do agree, and this is how I evaluate a lot of tools, but wouldn't it be easier just to have a web page? I'm not saying that I can't use this, I'm saying that it would be far more convenient for me (and likely many others).

Its more of a large inconvenience - I don't develop on my computer, I write all code on servers in my company's cloud. My choice would be to either clone this onto company hardware in the cloud or install node and the associated tools on my desktop.

While I doubt this applies to others, my issue here is that my primary work computer is running Windows.

Looks really fun, but is there any way I can play online without having to set up a whole environment for this?

I believe he is referring to the case of the interviewer being a peer rather than a manager.

In my experience the manager cares about fit and attracting you to the team, whereas the peers are all looking for reasons NOT to hire you.

This was posted multiple times in the last few days

https://news.ycombinator.com/item?id=16880991 https://news.ycombinator.com/item?id=16844285

This is a very reasonable task, but most of the take-home projects I've gotten (for both frontend and backend) have been significantly larger.

The worst one was for Optimizely, who asked me to write an entire website (front-end using React, backend in Python) which will display a list of products from a database, including full tests. I determined that boilerplate and configuration would take me about 5 hours, with maybe another 5-6 hours of actual coding. They even offered to pay me something like $15/hour (literally nothing) to do this. I said no.

This is extremely interesting and I'm eager to see the follow-up.

I'm currently planning something very similar at my company and any reference to how other smaller-scale companies handle this when scaling is invaluable. Are there any other blogs from other companies which have talked about similar things?

The target of this service is very much NOT people who would know how to use IRC and know where to go on IRC to ask a question, nor is the type of question which this service is aiming to answer easy to ask over text.