Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
kevan
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
40 ms
·
361.
▲
by
kevan
12y ago
"When you have a hammer, everything starts to look like a nail."
362.
▲
by
kevan
12y ago
As long as you're able to share sessions between services I think that would work. If you have multiple backend systems it may take some work to get session sharing implemented.
363.
▲
by
kevan
12y ago
> My suspicion is that more candidates than one would expect get hung up worrying about giving some sort of clever answer to impress the interviewer that they bobble it up a bit. I've definitely felt that pressure as an interviewee.
364.
▲
by
kevan
12y ago
Ooh, now we can add a big section on EMR, wireless protocols, forward error checking, the possibilities are endless!
365.
▲
by
kevan
12y ago
A concrete example: video upload and processing. Your frontend handles uploads, then you can offload conversion to AWS while you continue to handle other requests.
366.
▲
by
kevan
12y ago
Correct, there's no way to prevent people from seeing your keys.
367.
▲
by
kevan
12y ago
> Practicing slowly will never get you to perform things quickly. Learning something at a very slow tempo and then slowly increasing to written tempo is a strategy taught by many teachers and in my personal experience it's worked we
368.
▲
by
kevan
12y ago
I play trumpet, my routine usually starts with long tones and slow articulation exercises. As I get warmed up I extend into lip slurs, faster articulation, and flexibility. After I'm completely warmed up then I go into a mix of techniq
369.
▲
by
kevan
12y ago
> Stop thinking like a human. Think like a corporation. Corporations are like humans whose smallest increment of currency is the largest paycheck you've ever received. This is a pretty important point. The financial scale that a com
370.
▲
by
kevan
12y ago
I believe most CS students would benefit greatly from this type of class. The topic may not perfectly fit into pure computer science topics but it's something that anyone who writes code will run into during their career and should hav
371.
▲
by
kevan
12y ago
There's definitely a risk as a domain expert that you'll take things for granted. Henry Ford is a good example of this, he was never an expert in horse-drawn carriages but he changed that domain drastically.
372.
▲
by
kevan
12y ago
Lecture 20 of How to Start a Startup[1] touched on this. > In the beginning of a company, there is no management. This actually works really well. Before 20 and 25 employees, most companies are structured with everyone reporting to found
373.
▲
by
kevan
12y ago
That's the dependency injection[1] way to do it. [1] http://en.wikipedia.org/wiki/Dependency_injection
374.
▲
by
kevan
12y ago
> you also can't ignore everything new in the name of consistency and expect anyone to want to work on the project. The strategy will cause a variant of the Cobol effect. You'll either have to pay developers obscene wages to pu
375.
▲
by
kevan
12y ago
>Uber applied for a U.S. patent last year for “dynamically adjusting prices for service” using mobile devices. The system measures supply (Uber drivers) and demand (passengers hailing rides with smartphones), and prices fares accordingly
376.
▲
by
kevan
12y ago
The article followed the lecture[1] almost exactly, I don't think there was much added value in it. [1] http://startupclass.samaltman.com/courses/lec07/
377.
▲
by
kevan
12y ago
Assuming the thermister isn't very close to the heating element you'll be heating air for a while and the heating element might burn out.
378.
▲
by
kevan
12y ago
This looks like it'd be really useful for quickly making teaching materials.
379.
▲
Ask HN: What do your teams look like?
1 points
by
kevan
12y ago
|
0 comments
380.
▲
by
kevan
12y ago
Can you afford not to take this offer? If you have loans that need to be paid off then that may tip your hand.
381.
▲
by
kevan
12y ago
>Barriers blocking me from getting work done It took me too long to figure this one out. I had a habit of hiding what I was having trouble with because of fear of looking incompetent. Even if you're not actively looking for help on
382.
▲
by
kevan
12y ago
http://www.entrepreneur.com/article/222524 The article if you'd rather not watch a video.
383.
▲
by
kevan
12y ago
The first use case is one of my focus areas at work. We used to not be able to do functional testing until code was in the develop branch. Developers could work on feature branches, but we had no way of deploying these branches to a test en
384.
▲
by
kevan
12y ago
>then use database migrations (e.g. with alembic) +1 for Alembic, it makes database schema changes a lot less painful. It's definitely good to sit down and figure out high level architecture before building, but for small one-off pr
385.
▲
by
kevan
12y ago
>User agent detection sounds great, until you have a user that spoofs their agent. Do a significant percentage of users spoof their agent?
386.
▲
by
kevan
12y ago
>Not just a link to the Javadocs; preferably a "getting started" page I wish more java projects had python-style documentation. I can probably figure out how to do things eventually by wading through Javadocs, but they can be r
387.
▲
by
kevan
12y ago
Trying to avoid cleverness is a big one for me. Also, learning about patterns (both from books and from existing software). It can be pretty overwhelming to start a new project from scratch, but patterns provide a reference point to start f
388.
▲
by
kevan
12y ago
Agreed. Everyone makes mistakes, owning up to them shows maturity. Sidenote: I'd much rather find out about something like this before release than have someone exploit it in the wild and force a patch.