HK
Heykuki News
Top
New
Best
Ask
Show
Jobs
Toggle theme
Top
New
Best
Ask
Show
Jobs
Request
121.
▲
Setting boundaries at your job as a programmer
codewithoutrules.com
discuss
7 years ago
feross
2 points
122.
▲
Negotiate your salary like a 6-year old
codewithoutrules.com
discuss
7 years ago
itamarst
2 points
123.
▲
The cold incubator: the VC dream of workerless wealth
codewithoutrules.com
discuss
8 years ago
itamarst
2 points
124.
▲
There’s always more work to do–but you still don’t need to work long hours
codewithoutrules.com
discuss
8 years ago
fagnerbrack
2 points
125.
▲
Stabbing yourself with a fork() in a multiprocessing.Pool full of sharks
codewithoutrules.com
discuss
8 years ago
ingve
2 points
126.
▲
Python, fork(), and a multiprocessing.Pool full of sharks
codewithoutrules.com
discuss
8 years ago
itamarst
2 points
127.
▲
Why you shouldn't use the word “User” in your code
codewithoutrules.com
discuss
8 years ago
anw
2 points
128.
▲
Stabbing yourself with a fork() in a Python multiprocessing.Pool full of sharks
codewithoutrules.com
discuss
8 years ago
fanf2
2 points
129.
▲
Getting your boss to stop valuing you by time spent in the office
codewithoutrules.com
discuss
8 years ago
itamarst
2 points
130.
▲
How to be judged by your output, not your time in the office
codewithoutrules.com
discuss
8 years ago
itamarst
2 points
131.
▲
Does your job contradict your beliefs?
codewithoutrules.com
discuss
8 years ago
itamarst
2 points
132.
▲
Avoiding hour creep: get your work done and still go home at 5PM
codewithoutrules.com
discuss
8 years ago
signa11
2 points
133.
▲
Get productive faster at your new job–without working overtime
codewithoutrules.com
discuss
8 years ago
itamarst
2 points
134.
▲
Staying focused won’t make you productive
codewithoutrules.com
discuss
8 years ago
itamarst
2 points
135.
▲
Staying focused won’t make you a productive programmer
codewithoutrules.com
discuss
8 years ago
itamarst
2 points
136.
▲
Networking for programmers with very little free time
codewithoutrules.com
discuss
8 years ago
itamarst
2 points
137.
▲
The CAP theorem, a failed purchase, and a lesson on negotiation
codewithoutrules.com
discuss
8 years ago
itamarst
2 points
138.
▲
Programming as natural ability, and the bandaid of long work hours
codewithoutrules.com
discuss
8 years ago
itamarst
2 points
139.
▲
You are not your tools: programmers are more than the technologies they use
codewithoutrules.com
discuss
8 years ago
itamarst
2 points
140.
▲
How to lose technical arguments
codewithoutrules.com
discuss
8 years ago
Mayzie
2 points
141.
▲
Software Clown: 20 years of software mistakes, and how you can avoid them
codewithoutrules.com
discuss
8 years ago
mikecarlton
2 points
142.
▲
I took a sick day today, and that’s OK
codewithoutrules.com
discuss
8 years ago
itamarst
2 points
143.
▲
The futile comfort of working long hours
codewithoutrules.com
discuss
8 years ago
nautical
2 points
144.
▲
Not an expert? That doesn't mean you can't teach
codewithoutrules.com
discuss
8 years ago
itamarst
2 points
145.
▲
How to get a job with a technology stack you don’t know
codewithoutrules.com
discuss
8 years ago
itamarst
2 points
146.
▲
How to become a part-time programmer: an interview with an expert
codewithoutrules.com
discuss
8 years ago
wnm
2 points
147.
▲
The junior programmer’s guide to asking for help
codewithoutrules.com
discuss
9 years ago
mnmlsm
2 points
148.
▲
Your technical skills are obsolete: now what?
codewithoutrules.com
discuss
9 years ago
adamnemecek
2 points
149.
▲
Incremental results: how to succeed at large software projects
codewithoutrules.com
discuss
9 years ago
itamarst
2 points
150.
▲
Stop writing software, start solving problems
codewithoutrules.com
discuss
9 years ago
itamarst
2 points
More