Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
do
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
11 ms
·
1.
▲
Navigating Tech's Class System Without a Trendy Resume
(alltheotherthings.substack.com)
3 points
by
do
4y ago
|
0 comments
2.
▲
Write your feature announcement before you write code
(oshea.io)
3 points
by
do
5y ago
|
0 comments
3.
▲
Replace traditional interviews with paid pilot projects
(blog.laskie.com)
3 points
by
do
5y ago
|
0 comments
4.
▲
Automatic pool stick vs. strangers [video]
(youtube.com)
8 points
by
do
6y ago
|
1 comments
5.
▲
Why companies waste so much time in meetings
(laskie.substack.com)
1 points
by
do
6y ago
|
0 comments
6.
▲
Writing well
(julian.com)
279 points
by
do
6y ago
|
130 comments
7.
▲
Swaymass: A mysterious, AI-generated company
(twitter.com)
12 points
by
do
6y ago
|
1 comments
8.
▲
Elon changes Model S price to $69,420
(twitter.com)
1 points
by
do
6y ago
|
0 comments
9.
▲
Why Meetings Waste Time
(laskie.substack.com)
1 points
by
do
6y ago
|
0 comments
10.
▲
GitHub code reviews on demand from thoughtbot
(codereview.team)
1 points
by
do
6y ago
|
0 comments
11.
▲
Company Culture and Expectation Setting
(laskie.substack.com)
2 points
by
do
6y ago
|
0 comments
12.
▲
by
do
9y ago
Indeed | Full stack engineer (RoR or Java) | Onsite or remote | Austin TX | Full time We are looking for senior Java and Ruby engineers to join our team full-time. Our Assessments team has a simple mission: help candidates get the right job
13.
▲
by
do
9y ago
Interviewed (YC S15) | Software Engineer | REMOTE (US, Canada, Brazil) Interviewed builds job assessments that let candidates demonstrate their real world skills so that hiring managers don't have to rely on resumes, behavioral intervi
14.
▲
Emburse is amazing (employee credit cards)
(advice.interviewed.com)
3 points
by
do
11y ago
|
0 comments
15.
▲
Companies destined to die when fully-autonomous cars arrive
(advice.interviewed.com)
1 points
by
do
11y ago
|
0 comments
16.
▲
by
do
11y ago
We've been using Zube at Interviewed and really like it. We'd been using Github Issues previously but found it hard to prioritize our tickets in a way that was natural for us. The ability to drag and drop reorder our backlog has r
17.
▲
This is why the mobile web is dying
(advice.interviewed.com)
8 points
by
do
11y ago
|
1 comments
18.
▲
Interviewed launches to let job hunters prove what's on their resume (YC S15)
(blog.ycombinator.com)
3 points
by
do
11y ago
|
1 comments
19.
▲
by
do
12y ago
A QA test case management tool integrated with Github Issues. http://imgur.com/a/0oqGO Designed to be easy to navigate with the keyboard and replace the spreadsheets I normally use on projects. If anyone out there need
20.
▲
I don't know
(blog.42floors.com)
212 points
by
do
13y ago
|
77 comments
21.
▲
Why You Should Take a Digital Break (and 6 Steps To Do So)
(dumblittleman.com)
2 points
by
do
16y ago
|
0 comments
22.
▲
by
do
16y ago
This is not really a valid use case for meetup.com, which is good for recurring, topical meetings. Plus, its not free to start a new meetup.
23.
▲
by
do
16y ago
You really need to add searching capabilities or categorize listings by country/state to avoid scrolling every post to find something in my area that interests me.
24.
▲
by
do
16y ago
Listing any required years experience with a particular technology seems like a mistake. A good engineer is a good engineer and shouldn't need N+ years experience with a language/framework/tool to make an impact on a good team that's willin
25.
▲
by
do
16y ago
I would also add: how well do you handle rejection and failure?
26.
▲
by
do
16y ago
Anything that reduces friction for a user to get started with your product has the potential to be a good thing. But if your goal is to make money, and not just generate usage, I can see some possible problems with this approach. Not having
27.
▲
by
do
16y ago
What is the Chilean government doing to bring over already established, innovative companies? It seems that one good way to inject innovation is to introduce companies that can employ young, entrepreneurial Chileans and set examples they ca
28.
▲
by
do
16y ago
We are currently looking at the smartphone app approach. The phone approach was easier prototype which is why we started there.
29.
▲
by
do
16y ago
We started with the phone because it was easier to get a working prototype out the door and its truly a ubiquitous solution. We are looking at building an iphone and android app. Its starting to seem like a more viable way to make the servi
30.
▲
by
do
16y ago
We are considering a monthly fee, but for the economics to work we will need to be making roughly that $1 per hour of usage to cover phone call and other costs. We are still searching for the demographic that needs some sort of web content
More ›