Yes. I'm glad there was no glue. Battery was swollen for at least a year until I replaced it. I remember there were three screes holding it in place so there was no glue by design. Wish current macbooks would hold up to this kind of serviceability.
Perhaps the point of failure is not located inside the mechanics at all. I could imagine that dust is not necessarily always 100% non-conductive and might have an impact on pcb traces if their routing is very close (sporadic shortening).
Another interesting test would be heating up those microchips and see if potentially lose pins might be reflowed by this procedure.
curious if existing hardware can be upgraded later. i guess technically it might be feasable but vendors will try to make money and sell new hardware anyway. hoping for open router firmwares...
Reddit is certainly not a design with simplicity in mind. The sheer amount of links and navigation in general is completely overwhelming. I'd say it's rather a poor design.
Changing your life is one thing. leaving behind everyone this guy knows personally and potentially could help sounds like a big mistake... especially with anxiety attacks and severe depression.
Definitely _not_ the wrong place. Glad you do not give up and try to do something against your current situation.
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:
Apologies in advance if my comments below sound a bit harsh but I consider your arguments for using checked exceptions non-sense.
"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).
Just happened to me as well a few seconds ago (I actually had even 3 instances open in the background and no sleep/hibernation involved). But again just waiting for about 1 min finally led to a responsive system again.