I was denied a request to present, because my head of security didn't want to risk telling the world about my project. Now, they allow presentations, but I have no enthusiasm to present. Making it difficult has a lasting impact.
LP has a history of problems, but my company forces us to use that crappy product. I've complained about it for years. I use keepassx for personal, 1password for work, and lastpass for anything that I need to share with coworkers. I always wondered who got the kickback from LP.
LastPass is riddled with problems, and the quality has dropped precipitously since their acquisition by LogMeIn. For a sampling of their problems I suggest searching this site for their name.
Ok man if it works for you then keep on keeping on. I have chosen to leave the service due to a huge drop in reliability and several major security and service incidents.
Before I switched to another password manager, LP has:
- constantly managed to lose newly generated passwords
- consistently failed to register new passwords with the Safari extension
- failed to autofill credentials on many websites
I had used LP for years, but these problems never went away despite these being a failure of core functionality. After I finally switched to an alternative password manager, I was pleasantly surprised at how well everything seemed to work in addition to a much nicer UI.
In LP's defense, it's great that they offer such an important service for free, but I'd really prefer my password manager to be of more higher quality.
According to the Wikipedia article, I'm reading it such that the city commissioned a study that determined the city police force did target black people? Granted this is generations later.
In my experience, only the founders of startups make any money. If the startup is successful, then the founders walk away with millions. Everyone else would be financially better off if they worked for a large company instead.
Also, the executives of the startups take free trips and expense everything on the company's dollar. While the employees receive low pay.
I don't think the large companies are winning. The startups are killing themselves.
> Everyone else would be financially better off if they worked for a large company instead.
To be fair a lot of the change is because large companies are paying people so much these days. Barring large amounts of funding, a Series A- startup (based on the company being 0-2 years old definition of the article) simply can't compete with salaries.
Perhaps startups should start offering far more equity to early employees (I'm surprised you don't see more seed stage firms offering ~5% to senior devs) to compensate for the cash loss.
Nobody will give a senior developer 5% equity when even VCs only take 7% for the first investment that also includes access to professional networking events.
I think this partially the law's fault and partially example bias. I worked for a company who was acquired and I did very well especially considering I was a relatively new employee when the company was acquired. In other words, I think you tend to only hear about the bad stories because employees are pissed. In addition, the 90-day rule for stock options means early employees are rarely able to participate in an exit. I think if the law was changed to remove this 90-day exercise limitation, then a lot more employees would benefit from their shares/options.
I've worked at multiple startups and feel it isn't worth the effort. The execs always make out and everyone else doesn't make it worth their effort. The compensation will be better when working at established companies.
Rushed to office at 6am before important process was about to run that needed that host.
Plugged in keyboard+monitor, dead screen, nothing.
Physically power-cycled server.
Stood in front of monitor+keyboard. It occurred to me it was taking longer than expected to show POST screen. About that time, I got a page saying $ACTUALHOSTNAME is down.
Walk around to the back of the racks. The monitor cable had come detached from the cable extender that I plugged into the server. I had never plugged the monitor in at all, just the extension.
The server wasn't down in the first place, it just lost a virtual interface, which I was paged for, and stupidly tested that virtual interface instead of the REAL name/IP.
And then I raced to the office just so that I could cause an outage.
I once changed a piece of code that was referenced by every page on the customer facing site (10's millions of visits a day) to use a new function that someone had previously written (and was called on 1 page in the site). I mistakenly didn't really look to closely at the implementation of the function, and didn't realize how badly it's caching strategy was designed. When this code was deployed it instantly caused a thundering herd on our cache servers bringing the site down for about ~40 seconds.
My worst was that one time I accidentally took down some services that were essential for order processing via an unrelated, large stress test. My test accidentally consumed a large amount of bandwidth saturating the links to a shared service.
I did all this while sitting 2 feet from a print out of "The 8 fallacies of distributed systems". Bandwidth is indeed not infinite, can confirm.
Due to youth, totally misplaced confidence and poor access rights regime, ran an untested script in production causing it to fork uncontrollably requiring reboot.
