skysight-inc/HackerNews huggingface dataset:
I've been unfairly fired several times, so my advice is:

1. Forget it, that job is over, it can't be salvaged. Knowing it's over, do the minimum work.

2. Start actively looking. Even if you don't find a new job within 30 days, you'll start getting interviews in your pipeline.

3. If it's so bad that it's making you sick (trouble sleeping, etc.), then just walk away now. Otherwise, there are advantages to saying on to the end. They might offer you some salary as severance. You might be eligible for unemployment. Even if they do fire you, for legal reasons, they'll probably word it as a layoff rather than a firing for cause.

4. I'd advise against a whisteblower lawsuit. It's a lot of stress with no guarantee of winning.

5. Don't be sure that you'll be blackballed. There's always another job.
Arch's wiki + the lack of accidental complexity in their tools. Everything is very very tiny. It forces you to know the basic tools (grub,...) , and a few concepts (chroot, etc...). That said it took me years, even after CS college to be at ease with most things.
Agree with others - any relationship with your immediate superiors is already toast. Anyone who would retaliate against you for doing good work can never be trusted to treat you fairly again.

Considering that you want to stay at the company there are really only two ways this could turn out good for you: You bring this up the chain, effectively reporting your supervisor's bad behavior, and wind up reassigned under someone else, or you bring this up the chain and your supervisor gets fired. The latter is the only scenario that really gives you a good shot of remaining at the company without being hassled, and it sounds like your supervisor's behavior was bad enough to warrant their dismissal.

Some people do horrible things and their companies protect them. Maybe they're politically connected, well-liked, or valuable for other reasons. The way I look at this overall is that the company is either good enough to stop this sort of retaliatory behavior or they're not, in which case you shouldn't want to work for them anyways.

Good luck.
You have legal counsel and you're still posting to HN for advice? Have you lost faith in them? Do they know you're posting details of your case on the internet? Are they ok with that?
"When I raised that issue, he immediately began the process of putting me on a 30 day review, a necessary step prior to termination."

Document document document. Don't quit your job and when and if they do fire you. Sue. It sounds to me like your manger is retaliating against you because they are trying to cover something up. That is never ok and if HR is not handling it, than stand your ground and let the lawyers handle it.
SoundViz – We're International
This may seem obvious - but yes, consult others before using them as a reference. At a minimum, you'll want to know they're happy to give you a good reference.
One would hope you've developed a strong enough relationship with some colleagues as humans (i.e. beyond the confines of the "employee" relationship.) Humans don't always stay at one company forever.

Trust comes first - the rest follows rather easily.
TDD in iOS
> * Very difficult to parse

Irrelevant for a compiler target.

> * Esoteric type conversion system

Mostly not an issue, because compilers are not producing code using the type conversions.

> * Lack of integral type

JavaScript has integer support up to 32-bit, it just doesn't have 64-bit.
Page fails to render without JS.

Flagged.
Before you indignantly grep the web for jQuery, the post did say dead is hyperbolic. (Yeah, link bait...)

For web apps, jQuery is "dead" in the same sense that string-concatenated HTTP responses are dead.

They certainly exist and are used, but there is a level of abstraction (templates) that supercede -- or should supercede -- that functionality for most developers most of the time.

If I'm writing a "hello world" web server, I probably won't be using templates. But if I'm writing a web server serving HTML that I want to be maintainable at any non-trivial complexity, I'll be using a framework/library.

Sure, you can use jQuery, and yes Angular uses it (or jqlite) for cross-browser DOM interaction, but that will not be the predominant or most visible tool in any moderately complex web app.

Front end development is coming around to the advantages of MVC, and the current generation of tools reflect that.

jQuery is not dead; it is simply no longer the highest level of abstraction for creating web apps.
It can, I was just trying to be clever :P

For one, I don't need to drag monads into function composition:

fizzbuzz i triggers = map (\x -> fromMaybe (show x) $
mconcat $ triggers x)
[i..]

fizzbuzz 1 $ \i -> [["Fizz" | i `rem` 3 == 0]
,["Buzz" | i `rem` 5 == 0]
]
I dunno. Maybe the job is worth fighting for. And it definitely wouldn't be the first time someone went over their superior's head and won. Or got transferred to another division.
If I were in this position I would find the appropriate internal legal counsel and cc them on the email, including the words 'client attorney privileged and confidential' at the top. This affords some protection against discovery were the information to become relevant in legal proceedings. Taking that additional caution on behalf of the company shows professionalism on your part and will be appreciated by management who will see you're trying to contain and redress the situation rather than put the company at risk, in which case you may be seen instead as the risk.

Another thought- it's possible that your supervisor's manager is aware of the action being taken against you. You might be able to get better advice talking to someone in a different reporting chain if you can find them.
>blackballed from most firms in this city

Why? Do you have some kind of Public Hall of Shame where you put those who have been fired? Or do you live in some small village where everyone knows everyone and everything? Really interesting.
"I complete your challenge, I don’t get paid, I get thrown into the street and starve"

This assumes you're not currently employed

"nobody can expect to have “a relationship which lasts many years” with any company"

If I'm taking a job I'd like it to be a place that I could see myself staying for a number of years. It might not work out that way, but it's my goal.
I completely agree that we need comprehensive documentations. That's irreplaceable when you need to properly configure something. Good manuals are mostly used as a reference.

The Arch Wiki is something different. It guides you step by step how to reach your destination, and that's what most of the users need.
I'm skeptical that there is anything massively different between the technology Theranos uses and that used by existing clinical diagnostic labs.

Their greatest claim, as least in the popular press, appears that they can do these tests on "a few drops of blood" (it appears to be about 0.5 ml from the image) as opposed to 10 ml or so. This claim is nothing special, as in fact almost all tests are eventually done on an aliquot no larger than a few microlitres that is withdrawn from the larger sample. As to speed of results, this would likely be linked to organizational efficiency rather than a technical innovation.

Further, there is no way all the tests shown on their website can be done with one 0.5 ml sample, as samples need to be collected into different anti-coagulants for different tests as some anticoagulants interfere with some tests but not other (this is why the doctor usually takes two or three samples into different tubes -- not because s/he needs 30 ml of blood).

They may however have improved automation, or a better run or cheaper service, in which case, good for them.
HTML [+ CSS] themes for files exported from [Emacs] Org mode
Evolution of Laptop Keyboards, No More Page Up/Down Keys
I have not lost faith, and nothing I've said is legally problematic. Truly, I value the advice given here, and having weighed the risks carefully, I made a considered decision. It could be totally wrong, but for now, what's done is done. Thank you for reading this, and your advice is very well taken.
Here's a good post about why Javascript is not performant and probably won't be for a very long time. http://sealedabstract.com/rants/why-mobile-web-apps-are-slow...

The reason this matters is that we are inherently limiting ourselves to JavaScript's characteristics. We definitionally cannot get better than JavaScript since it is our standard.

If we could get all the player involved to agree to a new Bytecode standard, we could get better performance, and better standards. We might not have to even use a new standard. JVM's bytecode could work. .NET even.

Sure, as time goes by, byte code would need improvement. It would need additions or corrections. This is just the fact of a human world. To say we shouldn't do something else because of the fact that change exists, again, limits us.

Look at what we've got with real bytecode targets. Scala, Clojure, F#, C# and VB.NET to name but a few. They each target a specific family, and they perform well. As a result of targeting a more robust bytecode, they out perform JavaScript.

While I agree that we shouldn't throw out JavaScript anytime soon, I would like to see a more efficient interchange and structure for web projects. The Web and its browsers appear to be the future. Let's try to do better than a hacked language made 25 years ago by a defunct company.
I think people often discount the value that a change like this can have in readability.

For the longest time I was impressed by sophisticated/clever code that did hard things. As I built more and more systems I realized that such a perspective was futile that the better code in my mind was that which was clear, easy to read and understand the intent.

Any language changes whether they be core to the system or simply syntax sugar, any changes that make code more readable are by and large, good changes.
It's a recommended client now: http://redis.io/clients#nodejs
Being faster than PHP 7 for a few functions from bench.php isn't very convincing.
It is one thing to say that a two year old is randomly hitting buttons on your phone until it accidentally makes a call. Its shiny, it lights up, etc. It was another thing completely when at 9 months or so my daughter could consciously open the photos app and then scroll left and right to look through our family photos. Just because they can't talk yet they can still comprehend things and will happily learn sign language (taught her that at 6 months) and can use a touch device to accomplish things.

And as for screen time I have no regrets about letting her play various alphabet games on the ipad* to keep her stationary on the potty during toilet training.

It was weird realizing that she might never buy a keyboard.

*along with books toys and anything that would keep her there
Don't worry too much about the impact on your career. People know that these things can happen. The recruiters might have had similar experiences themselves. Fight if there is an injustice and then move forward. I wish you luck !
This is absolutely essential advice. Consult with a good employment lawyer as soon as possible. They will know the legal issues at play and can counsel you on what steps to take / not take. Unfortunately, it sounds like you may be in a situation where a single misstep could be used against you. You need an understanding of what your rights are, and what your protections may be under the law. A good employment lawyer will be able to help with that.

In the meantime, I would begin a journal and start taking notes (with dates/times) on what you have been told, observations you have made, etc. This may be helpful both to the lawyer as well as anyone else when you are asked to recall things. This way, it's contemporaneous note-taking as your reference, and not some attempted recollection from some time considered long past.
Show HN: Markdown on `console.log`
On Android you could accomplish this, but iOS has some fairly inane restrictions around running any type of VM. It's enforced somewhat arbitrarily, but it lets Apple yank any VM or app-hosting type thing on their whim. It was originally put into place to keep Adobe Flash and Air off iOS.

I also disagree that you always need mobile for everything. This seems geared toward communicating and collaborating, so yes mobile would be a must for mass adoption. But if it's geared toward devs or professional work that's not necessarily true.
Before proceeding with the steps to ensure your personal future, spend some time thinking why it's you who's involved in this? Why are you put in such a situation, possibly in the role of a whistleblower? Is there something greater that is screaming to be done regardless of how you will personally survive? Don't literally think but take some time to listen to something inside of you. Maybe there's a call for you.

If you're sure there isn't, the next step is to go practical.

Stop thinking you will not get a future if you get fired. The future is not set. There's very little, if anything, a manager or even a company can do to prevent you from getting another job in the same city. Getting fired because of not agreeing to unlawful practices trumps bad-mouthing any day.

Make a local copy of the evidence and store it safe. If someone wants to play hardball you don't want your position to rely on your word or anyone else's. I'm not a US citizen but if there's something done not according to the Federal law I could imagine some Federal authority might be very interested in it.

Start looking for a position elsewhere. Consider your job done: don't look back. You can do that later when you're safe in another job but now is not the time. You can take a "lesser job" because you can explain it away as being fired because of not tolerating unlawful practices. At least you have your feet on solid ground again.

Then escalate the matter to your manager's boss or his boss. There should be someone in the company (or someone who's invested in the company) who's interested in unlawful compliance documents. If there isn't, run fast and don't look back.

If the compliance matter reaches parties outside the company and nobody in the company wants to do anything about it, go talk to the police if non-compliance could cause harm to other people. If the matter is company internal, leave it there: the company will eventually sink with all their baggage if they tolerate such practices.

Once you've made a plan to survival, cherish the opportunity. What would you have wanted to do if only things hadn't been so good as for your employer earlier in time? What could you try now that you're off the hook anyway and have no reason to hold back to something? What are the things are have been impossible but could now be chosen?
There's a huge win in compiling to JavaScript, though: there's a standard that more or less fully describes the language, and there are multiple competing implementations. There are weird corner cases in JavaScript, but they're at least documented. That's more than can be said for most other languages.
The VA is a big consumer of medical services.
There's no one answer. Instead, it's a combination of factors that others have touched upon - closeness or influence relative to the decision makers, "force multiplier" effect, good old supply and demand. Instead of reiterating the point, I'm just going to get right in the face of the commenters who think it's unjust that managers tend to make more. I'm just a developer myself, I've never been a manager, but come on, let's not be total a-holes about this.

(1) It's just wrong to measure managers by the same yardstick one would use for individual contributors. Of course people who perceive themselves as the most technically proficient believe that less technically proficient managers should make less, but there's no rational business case for awarding pay on that basis. What managers do and understand might not be as technical, but that doesn't mean it's less important for the bottom line.

(2) You're probably wrong about the technical-profiency thing anyway. Sure, managers might not understand your favorite two-year-old technology as well as you do, but it's highly likely that they know some other still-relevant technologies better than you and have a better "gut feel" for technology overall.

(3) Business sense and general technical judgement are harder to hire for than narrow momentarily-relevant skills. Also, what managers do is often a lot less fun than what developers do. Who wants to spend all day every day in meetings or dealing with budget/personnel issues or balancing long-term development with the fire drill of the day? Thus, even if what managers know were less intrinsically valuable than what developers do, the demand for good managers would still drive up pay.

To flip this on its head, think for a moment about what the world would have to be like in order for managers not to make more (in general - I know there are already plentiful exceptions). Then you would have less technically able managers, making worse decisions, not resolving interpersonal issues, pushing more work onto the team or onto HR. Whee. What fun. Instead of grousing about it, accept it as the way as the world and get on with getting ahead yourself.
Bottom line for programmers :

You are guaranteed a very well paying job for a really long time.

That may certainly be the case, but the conclusion doesn't follow from your anecdotal premise. Otherwise auto mechanic would be a prestigious and very well paying job, as well. Now you might respond that modern vehicles have ever more complex computer technology and mechanics' requirements are changing in that direction. That much is true, but it mostly involves employing and inspecting black boxes. If anything, it should be a cautionary tale for vendor lockdown.
We used to hire 25-30 year olds in my shop, but we're finding health care premiums are much more affordable for toddlers.

Also by the time people reach 25 or so it gets harder to find individuals who are accomplishing new personal bests at the rate of two and three year olds. Most people have more or less plateaued by ten or eleven.
Excellent landing page: it explains exactly what it does.
Comments:

- try to make your case above the fold: "zip, click, demoed!" and picture does not convey any information.

- fix some "beautifications" issues (checks are ugly, etc.)

- make it "bare": that will also convey how easy your product is

- add demo
Really? In my experience, across (software/tech) in multiple industries - people (work friends, and work friends who you keep as real friends) help each other out if they're leaving (again, assuming we think well of each other and the references are honest) We don't assume interviewing equal disloyalty. A fair bit of caution is required, of course - but I see this happen all the time.
Heck, I've had executives who will help you if want to leave (again - it's not disloyal), and I've carried that same approach to those who reported to me.
Well, for one thing, every instance of mission critical hardware needs a full test, because hardware is messy and stuff happens. You wouldn't want someone hurt because a gate on a chip got a stuck-at fault or one of your vendors had a little extra variation etc etc.

Software only needs testing when the tools or inputs change. So design for testability of software is driven by the needs of a development group (eg simulators, debug statements), while hardware (at a minimum) is aimed at a post production group (eg JTAG, test fixtures).

I agree there are many parallels, but I think the culture is different.
Unfortunately in such situations there's little you can do legally unless you have a good trail. Regarding reporting up, do read some of the advice here as to whose side HR would take : https://news.ycombinator.com/item?id=8600716

Since the damage has already been done (putting you on a performance review), the rest is just a matter of time. By damage, I don't mean any damage to your reputation outside the company though. It's better to start job hunting while you weigh your options about a legal case or talking to higher-ups. In most of the cases I've seen, it's easier & cheaper to just walk away. However, if you are very confident that someone higher-up would be genuinely interested in knowing the truth, then you should get in touch with them. Whatever you decide, start searching for jobs.
That's not really an optimal way to check divisibility though, if you want to be quick try:

fizz = (uint)i*2863311531 <= (uint)i;
buzz = (uint)i*3435973837 <= (uint)i;

Should work for fine for i<=1000.

Edit: changed "<" to "<=", otherwise it fails when i=0.
curtis is the web app developer, bob is the CEO, jeremy is the directions operator:
Name:CURTIS J BUGAI
Date of birth:1978-03-28
Addresses:
667 Marway NW Comstock Park, MI 49321
5851 Stonecrop Dr NE Belmont, MI 49306
6133 Coach House St East Lansing, MI 48823
866 BEECHLAWN CT EAST LANSING, MI 48823
Social Security Number: 362043005
IP:67.208.241.241
Operating System: Windows 8.1
Browser:Chrome 41.0.2272.89

Name:JEREMY WAYNE DERUITER
Date of birth:1979-08-29
Addresses:
323 W Holmes Hall East Lansing, MI 48825
69 Lakeview Dr Delton, MI 49046
412 Stoddard Ave East Lansing, MI 48823
323 E Holmes Hall East Lansing, MI 48825
323 W Holden Hall East Lansing, MI 48825
4398 Okemos Rd Apt F110 Okemos, MI 48864
1566 Cambria Dr East Lansing, MI 48823
Social Security Number: 370048642

password:fredfred

phone number:517-913-1986

Name:MICHAEL JAMES MCFALL
Social Security Number: 365968188
phone number: 517-482-8145
addresses:
206 E Grand River Ave Lansing, MI 48906
1027 Morgan St Lansing, MI 48912
108 S Hosmer St # 211 Lansing, MI 48912
416 Farmdale St Ferndale, MI 48220
108 S Hosmer St Apt 21 Lansing, MI 48912
117 S Hosmer St Lansing, MI 48912
108 S Hosmer St Apt 18 Lansing, MI 48912
2476 Bolsover St # 601 Houston, TX 77005
115 W Allegan St Fl 6 Lansing, MI 48933
1436 W JASON RD DEWITT, MI 48820
1563 BLUE HERON DR HIGHLAND, MI 48357
1232 FERD HICKEY RD KNOXVILLE, TN 37909
It's poor decisions early in the project that make it harder and harder to add features and fix bugs reliably and quickly. And, like debt, it has a compounding effect upon the rest of the project.
Wikipedia is frequently as good, and occasionally a better reference, than WebMD or other sources (I generally prefer Mayo to WebMD which is frankly spammy as fuck).

And Wikipedia's fully syndicable.

Improve Wikipedia medical content, syndicate.

Problem solved, laws unflouted.
http://paperjs.org/
The trick is to make it very ergonomic to return the error. I thought Scala had do notation to make this the case. In Rust, the try! macro (which returns on error) is shorter than almost any other way to handle an error, so people usually use that.
It's a blackbox re-implementation. In Python, things are done different from C and there are other libraries are available (Pygments for instance). I also don't want to claim that it is as powerful as Vim is. But it should be stable, easy to install, and especially usable for Python development.
tl;dr It's basically a tech demo for systemd, and the systemd-nspawn tool in particular (which you might recall recently gained Docker format support).
Q: Why Python?
A: The only alternative would be Haskell, but I still have to learn that.

Wow, that would be interesting.
Not sure about iPhone, but there are AdBlock plugins for Android, and the hosts file itself is accessible if you jailbreak.

Better: install CyanogenMod.