I thought this too until I learnt what tinnitus actually is. Tinnitus isn't your ear ringing, its you losing hearing from loud noises and the loss of said hearing fucking with your brain and then due to that your brain creates that ringing noise.
Look up IIH and POTS. Read through descriptions. Good clue is if symptoms are worse after laying down for awhile.
Then schedule appointment with a neurologist or neuro-ophthalmologist or both. The real test is a spinal tap to measure pressure. They will also drain off fluid if high. I felt 10x better when they did that.
Medication is usually Diamox, lasix, topomax.
It can cause swelling in back of eyes, so sometimes eye doctors will notice first. But not always.
Interesting, however, I have experienced ringing in my ears after getting home from clubs/ loud music events only to wake up in the morning and have my hearing back to normal.
Not sure how ‘temporary tinnitus’ can be explained by this theory.
Hedge Funds don't invest in trailer parks, if they did they wouldn't be hedge funds they would be PE firms or REIT's.
While the US Industrial Complex is a cancer to the system I don't think they're to blame for Russia invading Ukraine. Instead, the US government needs to stop non-bid contracts and paying these companies "cost + Percentage" contracts.
Also the FP article misses out on a lot of nuances in the futures markets but thats a bit too much of a pain in the ass to get into.
There is a lack of cybersecurity investments in almost every industry. The issue is that the executives making the decisions 1) Usually aren't knowledgable about CyberSec and 2) don't justify the investment because it's not something they can physically point at and take credit for. .
The "economist" proposed a solution: tire cyber-security incidents to the stock market. The approach proposed was something akin to "have someone count and display the incidents of each company and blast radius". I'm not sure if this would actually work.
The other capitalist option is to make cybersecurity insurance mandatory, and impose high fees both to reimburse victims and to some government watchdog/agency (yes, government watchdogs and capitalism can co-exist). Then, it will be in the insurer's best interest to have clients with adequate cybersecurity implementations, and the market can sort it out.
At the same time, we should make sure that any insurance company that chooses to pay the criminals instead loses their license to operate.
If they sent me a home test with a custom programming language I would laugh and tell them to withdraw me from consideration. I'm busy, I'm not learning a new language so that you can pat yourself on the back, others might, but I won't.
I'm looking at this from a PM's perspective and not a devs perspective so take it as you will.
>he basically tells me this project should have been finished a long time ago and he can't believe it's taken this long
>>Sounds like a manager with a MBA and lack of hands on technical experience.
>he says I probably just misinterpreted an offhand comment of hers as a hard requirement
>>The problem isn't you not understanding her requirements, its a lack of documented well defined requirements - and any changes to said requirements should be noted and tracked.
>no longer necessary due to changing requirements
>>Once again, this sounds like your manager is deflecting the fact that they didn't have well thought out and well defined requirements before the project began.
It took me a long time to learn that it can be very valuable to stay in the loop with PMs and planners. Once, I was tearing my hair out over a huge task, and literally on the verge of quitting in shame, having realized it was beyond my ability to even move the needle on that mess. Fortunately I happened to vent about it to a PM, and she just says, "Oh don't stress out about that. That's getting cancelled." I don't know who was going to tell me or when. But as a mechanically-thinking engineer, my only solution to this was to figure out how to move the moon with a lever. Their solution was one line in an email that said, "Cut it."
I generally suggest that all dev teams send at least one person that's in the trenches daily to the steering committee meetings and any other decision making meetings.
This way, there's always someone that can keep expectations in check and can relay any minor/major changes back to the team. Ideally, these would be the tasks of a competent PM/Sr.BA but it doesn't always work like that.
