Hacker Newsnew | past | comments | ask | show | jobs | submit | GreeningRun's favoriteslogin


I probably have a whole personal blog of my own on the topic, dear as it is to my soul.

My two main pieces of advice: The bar is very very low, and share your burden quickly.

99 times out of 100 you are way overestimating the value of what you're delivering and people's expectations for it, and underestimating the value of time i.e. shipping quickly.

I've turned in so many things I'm not happy with and gotten a "this is great" that now I frequently just send over pseudocode, whiteboard sketches, and bullet point design docs to just get going on the feedback loop. Nobody has ever said "this is so bad we can't use any of it."

I also realized I do much better finishing other people's work than starting my own .. and so does almost everyone else. Bringing other people in overcomes "the boredom paradox" of a looming deadline - working with other people has its own challenges, but it is definitely not boring!

One specific thing I did that helped a few years ago at my precious company was I told my team, wrote in my email signature, ran a small study group, etc. On grit, procrastination, and "growth mindset" and just made a very intentional effort to tell people how I struggled with this problem.

So many people shared the problem! It really gave us a nice community and helped us (and management) recognize some of these issues, lesrn some new techniques, and get better at coaching, setting expectations, and ultimately managing the work.

So maybe last piece of advice is be open if you have these issues.


Hardware

- VoCore Lite

- USB to ODB2 cable

- Murata 1" x 1" DC-DC converter

Software

- Your choice of Linux flavor

- FreeDiag, looks like it is still under active development: https://github.com /fenugrec/freediag/

- Your own glue code to consume data, munge, and send updates.

I think I might do this. :D


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: