Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
wpeterson
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
15 ms
·
91.
▲
by
wpeterson
15y ago
This is a good write-up on how to build this, but it should be stated if you've grown beyond what subversion can do you should switch your repository over to Git or something with more advanced functionality built in.
92.
▲
by
wpeterson
15y ago
As an employee, understanding the liquidation preference and total shares outstanding are the two most important factors in valuing your stock options. Good to see more explanation of the role preferences play.
93.
▲
by
wpeterson
15y ago
Some quick advice: 1) Pair Program w/ someone Senior - best way to learn is to ride shotgun, literally. 2) Fix bugs first - trace a single feature, take things apart 3) Use the Source - Make sure you've got the source to both the primary pr
94.
▲
How PatientsLikeMe.com Monitors Ops w/ PagerDuty
(blog.winfieldpeterson.com)
6 points
by
wpeterson
15y ago
|
0 comments
95.
▲
by
wpeterson
15y ago
Rackspace support leaves much to be desired but it's 100x better than even Premium EC2 support (in my experience).
96.
▲
by
wpeterson
16y ago
Agreed. I find talking about exactly what story you're working on and how you moved it forward helps, since people can get bogged down in things outside the scope of the story/feature.
97.
▲
Guerilla Scrum: Minimum Viable Process
(blog.winfieldpeterson.com)
14 points
by
wpeterson
16y ago
|
3 comments
98.
▲
Postgres Hacks for will_paginate
(tech.patientslikeme.com)
5 points
by
wpeterson
16y ago
|
0 comments
99.
▲
by
wpeterson
16y ago
+1 for turning art, an awesome service with some great people behind it. I find that product a lot more appealing than renting/shipping originals without a purchase.
100.
▲
by
wpeterson
16y ago
I was surprised how much of a load webcrawlers (Google, Bing, Yahoo, etc) imposed on us at PatientsLikeMe, the majority of which is Google. The "intelligent" rate limiting results in a very high rate of crawl for many sites. We added addit
101.
▲
What Makes a Great Startup Engineer?
(blog.winfieldpeterson.com)
3 points
by
wpeterson
16y ago
|
0 comments
102.
▲
by
wpeterson
16y ago
Rails seems an ideal language for startups, but I was still surprised to see how highly it plays on HackerNews. Lot's of great quotes in this article from earlier this week about why startups in Boston are using Rails: http://bostinnovatio
103.
▲
by
wpeterson
16y ago
Well played
104.
▲
by
wpeterson
16y ago
http://www.sas.upenn.edu/~duckwort/images/12-item%20Grit%20S...
105.
▲
by
wpeterson
16y ago
The article came out well, happy to debate the merits of Rails as a platform in the comments here.
106.
▲
by
wpeterson
16y ago
Based on wmf's comment, I wonder if a more specialized role would make sense? Ops guy?
107.
▲
by
wpeterson
16y ago
That's a good point. I would imagine software engineering should be a core competency of every YC startup.
108.
▲
Ask HN: Why Doesn't Y Combinator have an Engineer in Residence?
2 points
by
wpeterson
16y ago
|
3 comments
109.
▲
by
wpeterson
16y ago
You’re conflating dogmatism for a lack of critical thinking. It’s more important to recognize that a given tool or process is made to solve a set of problems. If you don’t have those problems or have a better way of addressing them, you don
110.
▲
by
wpeterson
16y ago
This is why you need to hire full stack engineers, or have at least one on your team.
111.
▲
by
wpeterson
16y ago
Definitely interested in both code and your Redis config files.
112.
▲
by
wpeterson
16y ago
I'm puzzled to see such resoundingly positive feedback here. Props for the hard work on building this product out. However, in a world of smart phones I can't imagine ever using a watch like this. Watches have been relegated to primarily f
113.
▲
by
wpeterson
16y ago
+1 on the thesis - developers expert in the product, using the product. To me this should be the real goal and take-away from this article, not the many nice things this enables, but how to get there for other companies/products. THAT would
114.
▲
by
wpeterson
16y ago
This is a cool model, but I worry it only works because software engineers are both the producers and the consumers of the github product. The real take-away for me was less their means than how much freedom/less process you can get when th
115.
▲
Combatting Passenger Resource Collision at PatientsLikeMe
(blog.wpeterson.org)
1 points
by
wpeterson
16y ago
|
0 comments
116.
▲
by
wpeterson
16y ago
I wish he would write a proper blog entry and tweet a link to that.
117.
▲
File Handle Leaks in Hudson
(blog.wpeterson.org)
1 points
by
wpeterson
16y ago
|
0 comments
118.
▲
by
wpeterson
16y ago
I wish this TED talk were the topic rather than his older Atlantic Essay. Much better job of advancing and conveying his ideas.
119.
▲
by
wpeterson
16y ago
Assuming your data migrations are stateless and reversible.
120.
▲
Strange Rails ActiveRecord Timestamp Errors (Time =/= Time)
(blog.wpeterson.org)
1 points
by
wpeterson
16y ago
|
0 comments
More ›