Stratechery is always great and this piece is no different: The WeWork IPO – Stratechery by Ben Thompson.
What makes it good is that rather than just slamming WeWork superficially, as many takes have, it delves into what could possibly justify why WeWork is a good investment.
My take is that if WeWork had a different executive, it could be a successful company. I think the comparison to AWS is somewhat valid, and in the gig economy with lots of short term work, it could become very successful. (It worked really well for a recent project I was on).
That said, I believe the executive team of WeWork will not be able to handle any drying up of capital or a recession of any length. Or investors will wake up and ask themselves why WeWork should be valued way more than IWG/Regus. Time will tell, of course.
One last thing: my understanding is that WeWork had to start from scratch in terms of buying up / leasing real estate, but AWS did not start from scratch and took advantage of existing capacity Amazon currently had.
(Image link to the original piece in the article reference)
August 20, 2019 in ideas, new!
Tagged AWS, business, entrepreneur, ideas, investment, realestate, startup, strategy, WeWork
You’ll need some (not alot) of technical knowledge, an Amazon account, and this guide: Simple site hosting with Amazon S3 and HTTPS.
Going to give this a try myself soon.
P.S. This piece might help too.
P.S.S. Microsoft is getting in the game too. Click here for more info.
I used to be a haphazard reader and my reading had slacked off. In 2017 I decided to have a goal of reading more and recording the books I had read. For the record, I had a simple Excel spreadsheet. This was good, but not easy to share.
To build this page, All the books I have read since 2017 | Smart People I Know, I wrote a Python program to convert the Excel spreadsheet to HTML. After that, it make it look modestly better, I stole some ideas from here. I was going to put the HTML directly into WordPress, but there were formatting issues. I instead put the page in an S3 bucket at AWS. And voila! Done!
I just cleaned up an environment I had set up in Amazon years ago for a client. (The client wanted to use Amazon, so we did.) In doing so, I wanted to make sure I didn’t leave anything behind which would cause me to continue getting billed even though I was no longer actively using EC2. I believe that the following checklist was useful in insuring this.
My EC2 cleanup checkist:
- Delete my Elastic IPs
- Terminated instances – running and non-running (I did this before deleting volumes, since it deleted alot of them for me)
- Delete remaining volumes
- Delete my security groups ( 1 will be left – the default one)
- Deregister AMIs
- Delete snapshots (you need to deregister your AMIs before you do this)
- Check your account balance
- In a few days, check your account balance to see if there are any charges you haven’t accounted for
After following this checklist, my EC2 environment was cleaned up. Depending on how you are using EC2, you may have more things to delete. Checking your account balance will help there: if you left things behind, they may incur charges. An increase in your account balance will help flush them out.
One thing to consider: you may delete something, but it doesn’t show in admin console. If that is the case, logout and then in. I did that when I was having trouble deregistering my AMIs. I logged out and then in and when I checked them, they were now deregistered.