Think X-Files did a take on this but it was fungal infection instead of radiation
We already know they are playing politics in who they audit.
Same here. Got my first computer in '82, a TRS-80 Color Computer, paid for by frying chicken at KFC. Parents didn't want to pitch in because they thought it would be collecting dust in a month. I couldn't even afford a monitor nor disk drive nor software. I had to write my own code to do anything but that was the fun of it. The next big purchase later that year was an Epson MX-80 so I could print out papers instead of slaving over an IBM Selectric. That was fun as I had to write my own single line editor. The hardest part was getting the printer to work. Dad was clueless about electronics and there was no Internet so it was many nights of trial and error with help from hint found in borrowed copies of 80 Micro.
This project has failed because of poor leadership. They need to hire Office Space like efficiency experts and figure out who has to go, interviewing key people starting from the President on down. Surely if the Feds were a private corp and the President was the CEO, the Board would have ousted him years ago.
Ha! We get close to 80 OTA channel in the San Francisco area. But on 10-15 are in English
Best way to make allies at work is to spend your break time chatting with your co-workers. You should talk about non-work stuff but invariably you all will talk about work and that is how others will get an idea of what you are doing without cutting into your productive time. Also make a point of chatting with your boss when ever you see him/her in the hallway. Nothing deep, a simple "hello, how are you doing" will suffice if your boss looks busy. But you want to give the impression that you are an out-going employee that is part of the team. If you get more than a few seconds, ask how was their weekend and slip in something about your progress. The boss doesn't need the details but just the impression that you are working on something important and that you are making progress. If they boss doesn't know what you are doing, make sure to request a meeting where you can give a summary of your project and your future plans. Ask for the boss' input and advice if anything to make them feel like you respect them. If the advice is good, take it and build a working relationship with your boss. If the advice is bad, don't reject it outright but take it home and think about it, weighing the pros-and-cons. If it's still bad, formulate a friendly rebuttal on why some other direction is better. Sell yourself. Get buy in. Manager's don't like maverick's even if they are good at what they do.
Who ever thought it was a good idea to make over Yahoo! into a poor imitation of Google (and a broken one at that) should get an F on their review and escorted to the door. I used to use Y! Mail and Groups several times a day. Now I hardly use mail and don't use groups at all. Glad I left Y! 10 yrs ago. It stopped being fun they relocated from the Keifer complex.
I'm trying to be a good Dad and teach my kid to bully his classmates but it's getting harder and harder...
And how big were those countries? The smaller the population the easier it would be to implement. Getting single payer here would be like trying to get all of Europe on a single EU based system. I don't think you could do it unless you are willing to down grade the better run systems like Germany's.
How so? The law passed when the Democrats controlled both houses. Not a single R voted for it, nor were any needed to pass it, so the D's got what they wanted. In fact, R's were kept out of many of the planning meetings. The reason the law is bad is that it is much too complicated with many facets written as TBD at the HHS Secretary's discretion. The implementation is left to the amorphous bureaucracy. I don't think any of our representatives know what's in the law and none have read it cover-to-cover, at least not before voting it in. It's just too damn long.
If a start up writes up their code with best engineering practices so that the code will be maintainable 10 years out, you can be sure no one will be looking at the code 10 years out because you will have never launched v1.0 and you'll be out of business. When you start out, the first release just needs to be good enough to satisfy your initial customers and get to get some funding. Then once you have some stability you hire people to solidify the code and expand the user base.
Could they put it back in with Temuera Morrison's face superimposed?
That's because you're doing it wrong. Didn't you get the memo?
Most of the other issues don't bother me if the project is really cool. Plus with my productivity ramped up management tends to stay out my way. OTH, with boring project, everything on the list is 10x more painful. Unfortunately, for the typical programmer, their entire life is spent working on the former.
Unless you are doing something completely novel, don't reinvent the wheel. Look for existing libraries that are commonly used in your area of research. Then your language choice will be narrowed down to possibly only one. If by chance this library doesn't have the performance you need, it will be easier to tune it for speed as compared to starting from scratch. Unless you are in CS, grad school is not where you want to embark on a huge software project if the fundamental coding has already been done by others. You could easily "waste" 1-2 years writing and debugging code without producing anything publishable. BTDT.