500 karma · joined June 26, 2014
It's time to start working on next year's conference and grant proposal.
> I wasn't put on Pivot. My manager wanted to work with me a little bit to see if I was going to commit to the job. So they sat me down and said I could go on Pivot and leave right away, or they would work with me
So the manager probably put someone else on Pivot to meet their quota and when the author left now they are down two people. If they knew the author was leaving they would have ranked them dead last, put on PIP, and then part of their quota is met.
Also this quote shows the farce that Pivot is. It sounds like the manager did a PIP-before-the-PIP because they actually wanted them to stay and Pivot is just CYA performance for someone on the way out.
I've never worked at Amazon but people talk about Pivot coming with severance, but the author chose to leave for free. Maybe there's some disadvantage to accepting the severance? Not eligible for future rehire if you accept? Maybe it's just too hard to time getting a new job right at the conclusion of the PIP?
I think the end result is that it's probably not possible to pay employees with meaningful equity anymore so you'll have to go back to paying them the old fashioned way with money. I know I'm no longer willing to take RSU lotto tickets and a pay cut to work at a startup.
Not only do the investors have priority shares over employees, each investor can negotiate a guaranteed multiple. For example if they put in 100 million for 10% ownership but also had a 5X multiple guarantee and a sale price of 1 billion then the 500 million they walk away with ends up being 50% of the sale price. That part of the agreement isn't made public as far as I know.
Also, why get an entire domain to host a short blog post? Based on the copyright of 2004 and a .com tld registration of $10 per year someone has spent $190 to put this story out there.
I think there is a third possible cause to add to your list: companies exploiting something that maybe used to be sort of true but our parents hadn't realized it no longer applied. Collectible things might have been expensive and slow to produce when they were hand painted in upstate new york, then they started to be machine stamped across the world for pennies and for a while they could still fetch the old price and sentimentality as the market was saturated and then some.
I sometimes wonder if I'm going too far in the other direction and not sentimentality in at least a few things and preserving them. Maybe I'm setting up the pendulum swing in the other direction and my kids will have interest in collecting something when they grow up.
I don't live in the area but isn't the toxic dust of all the heavy metals going to be a problem? Is there some way to deal with that other than covering them all up with water so they don't get blown into the city?
The basic functionality starts off pretty easy to build so there's a large pool of people who decide to take a crack at it.
My parents worked at the defense contractor company on that site, E-Systems, for 30 years. I learned more about what they did there from this site today than I ever learned from them!
I didn't have a Windows machine so I stopped using Steam completely for a few years until the Deck came out.
Example: You click on an upvote button and it changes color, but there's 1 second of latency.
SPA: Color updates immediately, the "upvote pressed" http/websocket call to the server arrives one second later.
LiveView: liveview.js sends "upvote pressed" over the web socket, one second later the liveview process on the server gets the message, patches the dom and replies, one more second later the button changes color. Meanwhile the user has pressed the button 2 more times wondering why the color isn't updating.
There are phx-hooks (https://hexdocs.pm/phoenix_live_view/js-interop.html#client-...) to address this with small targeted bits of js where you can add event listeners but it can get messy quickly.
The last time I gave Jupyter notebooks a go it was a full session of installing and updating various Python tools: pip, conda, jupyter then struggling with Python versions. You end up piecing together your own bespoke setup based on other people's outdated bespoke setups you find while searching for your error messages. Maybe that's better now, this was a few years ago. For Livebook it's "download the app and run it." Other options exist and are well documented and straight forward. I set up a livebook server on our k8s dev cluster with a pretty simple Deployment I wrote just from looking at the livebook README notes on docker. We've made livebooks that connect to the elixir app running in a different namespace on the cluster. Very cool.
Once you have Livebook going the `.livemd` file is both version control friendly AND very readable markdown file rather than the big json objects used in `.ipynb`.
For Livebook rebuilding cells is a lot more repeatable. It also does a good job of determining if a cell re-execution is necessary or not if a previous cell is modified which can save you a lot of time. Likewise the dependencies installed are captured at the top so I've never had a problem when sharing a livebook. The other person always gets the same results that I had. I don't remember how it worked for Jupyter but it's really cool to collaborate with someone by both going to the same notebook session. It's like working on the same Google Doc but you are writing and executing code.
Now with the Publish functionality I can see using a livebook to throw together some functionality and share it with non-technical users in your org, while having it backed up to git for posterity.
I avoided Smart Cells for a while because I didn't like the "magic-ness" of the UI hiding what the code was doing, but as Jose has shown in the launch videos this week you can easily see the code they are backed with and replace the cell with the code if you want to take full control. Maybe it was always like that but I didn't realize it at first. They really make setting up stuff very easy without limiting you later on.