rauar
Another interesting test would be heating up those microchips and see if potentially lose pins might be reflowed by this procedure.
did Linus ever comment on the roll-back ?
edit: i'm not a radio engineer just saying based on practical experience.
edit2: just googled . congrats on having this guy on your team.
how is it going after 10 days ?
You should seriously get professional help. From what I read you seem to have had a therapy in the past and it doesn't work anymore. Did you try any alternatives ?
I'm sure other commenters can recommend professional where you live.
Wish you the best.
PS: I'm everything else but someone with good advice but to me a combination of medical therapy and mental training seems to be an idea (so that you do not rely on only one thing to work out)
Update: due to what you wrote in the 2nd paragraph here is what I found please make use of it:
http://support.twitter.com/articles/20170000-suicidal-and-se...
"It forces developers, who are often hurried, and who often make mistakes, to think about things that could go wrong, and deal with them"
Checked exceptions won't solve your problem here at all. If you need an instrument to force developers to think about things that could go wrong your team is screwed anyway.
"Much less time is spent reading and re-reading API documentation to make sure you've caught all the possible exceptions ..."
You are never ever going to catch all possible exceptions anyway (runtime exceptions and errors are still there even if you'd prefer to have checked exceptions only).
"Unchecked exceptions are a production run-time nightmare."
And you have to deal with them even if you use checked exceptions (again runtime exceptions and errors are still there). You have to have proper (unchecked) exception handling in the right places in your software.
Are you actually properly producing tests for your code before deployment-time ? Otherwise I would not get it why it would be nightmare.
"The best argument I've heard against checked exceptions is that they "bloat the code". It's true: checked exceptions requires more code.
Bloat causes development drag and makes the code more difficult to understand (more scrolling, jumping to different locations in the same file, etc.).
"But I'm writing code, not poetry."
I think you produce both.
I'd compare here checked exceptions to unchecked exceptions like what staticlly typed languages are to dynamically typed languages. And I've seen a lot of developers "loving" statically typed languages because the compiler tells them all their errors (at least they think so).
I always close the tab before closing the lid.
Just a side-node: the API docs were the biggest obstacle in the whole process. W.r.t to platform usage I think this would be one of the top prio things to get even more people using Three.js.
Or is it that I used the most trivial particle rendering ? :)
It happened to me one or two times that I thought the same because the dark color of the sea looks somehow more solid than the continents.
If it's really a rendering bug could you share a screenshot ?
- left-button and mouse move = rotation
- mouse wheel = zoom in/out
Plus real-time push visualization using node.js and websocket...