itamarst

44 ms·

421.
by itamarst 8y ago
This article has some good points, but it also suffers a lot from the author's extremely narrow horizons: - It's very US-centric. Public universities are AFAIK free or very cheap in Germany for example. The reason for rising costs
422.
When C extensions crash: easier debugging for your Python test suite(pythonspeed.com)
23 points by itamarst 8y ago|7 comments
423.
by itamarst 8y ago
I've been harping on this with evidence from other industries gathered by Evan Robinson ( http://www.igda.org/?page=crunchsixlessons ), but nice to see direct post-facto evidence from software teams. Some more reasons wh
424.
A small study shows crunch time makes developers less effective(blog.gitalytics.com)
2 points by itamarst 8y ago|2 comments
425.
You can’t avoid negotiating–but you can make it easier(codewithoutrules.com)
3 points by itamarst 8y ago|0 comments
426.
by itamarst 8y ago
Right, you don't want to omit things you've done if they're relevant. But ideal is to show natural progression, or if not then aspiration. E.g. intro paragraph can say "I am looking for job where I can take on more respo
427.
by itamarst 8y ago
Those statements are insufficient, since they don't say whose initiative it was to do the action. There's a big difference between "I wrote unit tests because my boss told me to" and "I spent 6 months pushing to fix
428.
by itamarst 8y ago
You can give context, and what you did. "After noticing the need for X, I proposed we build Y. As a team we build an initial prototype, and within two weeks we had revenue and hundreds of buyers." Example from my resume: "I c
429.
by itamarst 8y ago
1. I interviewed a number of people (and their stories are in the book), both as inspiration for readers and to spot more patterns than my personal experience. 2. A lot of time spent reading books, and even more importantly online comments
430.
by itamarst 8y ago
1) Wednesdays off are a popular choice yeah: see https://codewithoutrules.com/2018/01/08/part-time-programmer... who talks about it. 2) For salaries it seems like new job is better way to get big bump. For
431.
by itamarst 8y ago
Author here— It's about 27,000 words, so about a 100 pages at industry "standard" of 250-300 words a page. So, taken in a literal sense, yes. Does it need a book's worth of content? It depends. If you have a lot of exper
432.
You Can Negotiate a 3-Day Weekend: a book for devs who want a shorter workweek(codewithoutrules.com)
17 points by itamarst 8y ago|7 comments
433.
by itamarst 8y ago
You can imagine three levels of skill ( https://codewithoutrules.com/2018/10/10/beyond-senior-softwa... ): 1. Implement a solution someone already came up with. 2. Solve a problem someone gave you. 3. Identify
434.
by itamarst 8y ago
You can (sometimes) use GitHub to figure out if the company has bad work/life balance, e.g. if you see lots of employees committing code on the weekend on the same dates: https://codewithoutrules.com/2019/01/3
435.
by itamarst 8y ago
Pro tip: Don't work 70 hours a week. Beyond the impact on your social life, it also makes you a less effective worker ( http://www.igda.org/?page=crunchsixlessons ), so it's really not good for _anything_. Seriously
436.
by itamarst 8y ago
Working nights is massively counterproductive, and will make you less effective: http://www.igda.org/?page=crunchsixlessons As others said: - Learn to say "no" to people. You listen, make sure they're heard,
437.
by itamarst 8y ago
Formal methods can let you run your design through a checker that will prove it's correct. Hillel Wayne has blog posts, talks, and a book ( https://www.apress.com/us/book/9781484238288 ) about this: https:&#x2
438.
by itamarst 8y ago
Will assume you are programmer, here, if not the dynamic might be different. The presumption is that you get paid less when you work less. And this is true, to an extent: when I've negotiated a shorter workweek I've typically gott
439.
by itamarst 8y ago
There aren't any offers, sure, but you can still negotiate for this and get it—it's harder than doing it at your current job, but it's still possible. And once you've done it at one job it's easier to say "and
440.
by itamarst 8y ago
As others mention here and there in the comments: you can get a 3-day weekend at many tech jobs. It's just a matter of asking, and asking in the right way. E.g. this guy I interviewed has been working 4 days a week for 15 years: https
441.
by itamarst 8y ago
Looking at the docs it's been there at least since PostgreSQL 8.1.
442.
Farewell to fsync(): 10× faster database tests with Docker(pythonspeed.com)
5 points by itamarst 8y ago|2 comments
443.
by itamarst 8y ago
Never actually used it, but possibly dotscience.com might do something like what you want?
444.
by itamarst 8y ago
There's a lot of academic research about electronic voting. A quick search on scholar.google.com brings up https://pdfs.semanticscholar.org/9cb3/cd86b699b124348b21e936... , I'm sure there's much more more
445.
by itamarst 8y ago
It's probably a licensing issue, and NY Times can't share AP articles for more than a week or something. They link to this story directly on AP site in a followup story ( https://www.nytimes.com/2019/01/28
446.
by itamarst 8y ago
As a preliminarily step, work less, so you have the time to think about what you actually want to do. "8 hours for work, 8 hours for sleep, 8 hours for what we will" is a good slogan, though these days it should really be less tha
447.
by itamarst 8y ago
* First month on the job I wrote some software that took our biggest customer offline every night (would've been during the day too if I'd picked a smaller constant in my code). * Accepted a job for vastly less than market rates,
448.
by itamarst 8y ago
You need to _operate_ your software. The way a company with 10,000 software engineers operates their software is very different than how a company with 5 software engineers does it. Microservices are the prime example of thing you should ne
449.
by itamarst 8y ago
It's worth noting that "Design something that can scale to Google-size" is very different than designing smaller systems (and vast majority of systems are smaller systems).
450.
by itamarst 8y ago
1. Identifying problems, rather than just solving problems, makes you immensely more useful as an employee ( https://codewithoutrules.com/2018/10/10/beyond-senior-softwa... ) 2. Don't have a huge number of

More ›