jwn

ASRS (https://asrs.arc.nasa.gov/) is how both private and commercial (including ATP) pilots can anonymously and non-punitively share safety or otherwise concerning events.

The goal is data collection to assess and prevent incidents. NASA's intake on the reports are not anonymous, but their public reports are. NASA functions as the filter between pilots and the FAA/NTSB.

That's an interesting perspective, one I had never thought about yet rings absolutely true.

This happened to a company I co-founded. My common stock was bought at about 1/3 of the lowest price given to early employees for options. (I had RSUs, not options).

I got $130k, and their options were worthless.

Luckily the acquirer offered retention bonuses that helped dull the pain, but of course those are taxed at regular income and not long term capital gains.

Oh, and like a previous comment mentioned: the VCs have preferred stock so they get their investment back 100% before any common stock sees a penny. If employees had the same stock as VCs, I estimate I would have walked away with about $400k.

Well that's strange. The company was founded in 1976, so it was certainly plausible that they would be an early domain registration, but 1996 wouldn't qualify as that!

I wonder why you got a different date back?

This must be missing entries. For example, look up ca.com:

created: 1985-01-01

Making it 2 months older than the earliest dot com on the list.

I find cursing at the bot gets me to a human right away. It's also therapeutic.

Because the CEO skillsets to grow a company from 1-10 employees is massively different than the skills required to take it to 100 employees.

Can you offer any more insights? What's the reality behind OTS?

I don't know if any Fastmail employees read over this, but thanks for finally adding TOTP to the list of 2FA methods! I had been (uneasily) using SMS and wishing you guys would up your game, and I'm glad to see that you did.

Top Secret/Sensitive Information

Can someone explain what the use cases for this are?

Unlike the Juicero, bottled water provides added value in that I can have access to suitable drinking water when I otherwise would be forced to drink tap water.

Before someone replies that tap water is perfectly suitable for drinking: Sure it's safe, but I have never had municipal water that didn't taste bad. Never. Maybe I'm just spoiled because I have a well that provides tasteless water.

Anyone care to explain why SystemD is so contentious to the point it's worth forking Debian?

Maybe you can elaborate as to why this is the correct course of action? I've never heard of this office.

Awesome, nice find!

>> Canada for example says right on their immigration website that if you are working for a company not based in Canada and are paid from outside of Canada then there is no problem.

Where does the Canadian immigration site say this?

As far as the SEC is concerned you are correct, but it's possible to have additional (contractual) restrictions placed on a stock grant.

I assume the GP meant something similar to restricted stock, where you are severely limited in selling and transferring of your stock until certain preconditions are met (change of ownership, IPO, etc).

That's fantastic! I'm not too far from you (Lake Wallenpaupack region) and I've always wanted to start a WISP, but the lack of housing density out here makes it less than economical =(

I really want to love Rust, and while I understand the Rust borrow checker in theory, actually using it in practice has been a major headache. I tried Rust on a simple terminal-based project, and after a week of feeling that I was getting nowhere I switched to Go and had a proof of concept in several hours.

With that said, can you recommend a good source to really understand best practices and patterns for ownership and borrowing? I feel that's the biggest hurdle to using Rust (at least in my case).

I'm glad your charging for this. I took one look at the output and immediately decided that it's something I would pay for!

Buying it now...

But the Electoral College has nothing to do with the party primaries that stuck them with Trump in the first place.

"The group conducts the ritual, then each person files out of the room one by one, and then they all head to a restaurant and party."

Well, I now know where I would attack if I had any interest in a takeover of DNS.

Good answer, thanks =) My question earlier was an honest question, asked out of curiosity...

Looking at http://openjdk.java.net/projects/valhalla/, I don't see a whole lot of value compared to JDK9. What's your basis for wanting 10 so badly?

This would actually be pretty rad if I could narrow down the events to include only those from Github organizations that I care about.

I'm not sure what you mean by #1, the builds are as reproducible as the build system being used.

For #2, SourceClear doesn't build the software under test, it's hooked into the build via various methods. For Maven and Gradle, those are plugins. For NPM and Bundler, the existing build files contain the complete dependency graphs as determined by the build system. The analysis is quite accurate, I daresay more so than any other tool. Yes, it requires implementation work for each build stack, but that's the price you pay for accuracy.

In response to your #3, SourceClear doesn't report only vulnerabilities verified by call paths, it reports on all components will known vulnerabilities and denotes if a call path was found.

Disclaimer, I'm a Co-Founder and have spent a great deal of time writing scanning code.

I assume because they are both loops that spur off of 495. It's definitely confusing, but it seems consistency in numbering won out over unique-ness.

I've recently gone from Developer to Technical Product Manager, and I believe the following traits are important:

1) Communication on both a technical and product level. This allows you to act as a bridge between sales/marketing/management and the developers. See #2

2) Speaking two languages: Code and Product. This is where being a former developer comes in quite handy, as you can only learn Code through writing it, but you can implicitly pick up the Product by thinking like a non-techie and paying attention to what they care about.

3) Keeping a focus on the big picture during a project duration. As a Product/project Manager, you need to understand timelines beyond 3-6 months and make sure you're not shooting yourself in the foot for later. This is tangential to what you may have read in the Pragmatic Programmer.

4) Product/Project Manager can be squishy terms, meaning that the responsibilities can vary by company. Often you'll be left to ensure all the ends of a project are wrapper up: testing, documentation, communication on releases, etc.

There are probably many more things, but those are off the top of my head. Good luck!

I think that underscores the point about flexibility in naming operations ;)