Earlier quoted context omitted.
Tight IT band + weak glutes = culprit for a lot of hip injuries.
Tight IT band is an indication of bad form.
Ask HN: What did you learn the hard way?
301–310 of 322 posts
Re: Ask HN: What did you learn the hard way?
#302If you're a dev, don't work for a company where software development is viewed as a cost center--you want your work to be viewed as something that brings in revenue. (Learned the hard way when I worked at a large bank.)
I learned this from finance: Don't join a team that's mediocre and/or where you're the only one with your skills. When it comes time to evaluate your performance or assess how long something should take, your manager and your team will be clueless. Useless people survive by playing politics. And when you quit they'll play games you can't win.
Can you elaborate on this? Things to avoid when quitting such a position?
Re: Ask HN: What did you learn the hard way?
#303If you're a dev, don't work for a company where software development is viewed as a cost center--you want your work to be viewed as something that brings in revenue. (Learned the hard way when I worked at a large bank.)
I agree with this full-heartedly I work for a company where my boss told me a couple months in having a dev department was a waste of money for the company, and we were lucky to have a job. The company bread and butter was software that transcribe medical records from paper to digital. What the CEO and sale force didn't tell anyone it was actually a cubical farm of humans transcribing it all since the software was ho…
Re: Ask HN: What did you learn the hard way?
#304A few things: 1) People's words are like deep water. Pay careful attention to what people say--it's profoundly revealing (more than they realize). By listening, I've been able to identify people who intended to trouble me in some way. It's incredible, they just can't keep it inside even when pretending to be nice. 2) Actions speak louder than words (given #1, this is really saying something). Don't look for people to…
Could you expound on (1). I have been toyed around by my former Co founder who sweet talked me into believing him. I still think I suck at understanding human behaviour and nature. Are there any telling signs that help you?
Re: Ask HN: What did you learn the hard way?
#305Documentation is like sex. If it is good, it is good. If it is bad it is good
If it is good, it's great. If it is bad, it is better than nothing.
Re: Ask HN: What did you learn the hard way?
#306Re: Ask HN: What did you learn the hard way?
#307If you're a dev, don't work for a company where software development is viewed as a cost center--you want your work to be viewed as something that brings in revenue. (Learned the hard way when I worked at a large bank.)
Re: Ask HN: What did you learn the hard way?
#308Re: Ask HN: What did you learn the hard way?
#309Earlier quoted context omitted.
I think the calcified disinterest in some of us comes from being raised in (and eventually leaving) a Western religious and conservative environment.
Certainly true. The pointed rejection of all forms of religion after having been wronged by it is common, and Slate Star Codex makes mention of it in a note that's somewhat relevant to this topic. My personal hunch is that it mirrors an experience my friends have described about sushi and coffee, neither of which I enjoy. Apparently, bad versions of those things are unpalatable if you don't know what would make them…
I do have a passing interest in Buddhism (but not as an adherent, though I do meditate, read about, and appreciate some of it) though both Buddhism and the better forms of Christianity I still don't think are for me (nor is any organized religion) but I can appreciate parts of them from a distance and those that are still adherents, if their actions follow positive paths from them. I think I've matured since my journey out of the faith began, so it's easier now to be a bit more measured (yet still firm) in my rejection of it.
Re: Ask HN: What did you learn the hard way?
#310Earlier quoted context omitted.
"Our code is self-documenting. If you need documentation then the code isn't written well enough" -Assholes who don't know what it is like to work with mature code bases.
"Our code is self-documenting. If you need documentation then the code isn't written well enough" -Assholes who don't know what it is like to work with mature code bases. - People who don't know how to write clean code
"Our code is self-documenting. If you need documentation then the code isn't written well enough"
-Assholes who don't know what it is like to work with mature code bases.
- People who don't know how to write clean code
- People who think that not only they figured out what 'clean code' even means, but that everyone else will agree, thus single-handedly ending some 50+ years of heated industry-wide debate, numerous billion-dollar attempts by some of the most talented people in the world, and troves of 8-dimensional mental gymnastics about design patterns by way of a $21 ebook, a code review and some blog posts