cameroncf

Early 80's, when I was 6 or 7, my best friend had a pinball machine in his basement. The front door "hatch" to it was unlocked and we spend countless hours poking the insides with a long screwdriver to trigger various component. Probably wasn't safe but it sure was fun!

It's been covered for at least the last 5 years by many reputable news orgs. That HN link (you looked at the link right?) includes several refs, and a Google search dozens more.

First thing that comes to my mind reading this article is that they are just saving it all up to build the Nauvoo from the show "The Expanse".

I feel this article 100%.

Too many people think that remote work means "working from home" or that co-working means "working from WeWork". There are tons of different variations that let you get out and be around other people while working remote. I have long wanted to start a small fun workspace with space for 5 or so people that's really just a place for us all to do work together without being in a traditional office or our houses. A space we can define ourselves (or I define and invite others) that is not my house and also not a stuffy office.

IMHO - This is the future of work.

The biggest problem with Amplify is not any of it's underlying technologies. These are all great services. DynamoDB is one of the best things in the entire AWS service portfolio.

The biggest problem with Amplify is that it hides complexity that the developer really needs to have a firm grasp of when designing their application. You really need to think a lot about your access patterns before using DynamoDB. DynamoDB is OLTP and not OLAP. You aren't going to have a ton of ability to do ad-hoc queries with DynamoDB. that's just not a use case it's well suited for.

HOWEVER - AWS Amplify is marketed without that warning - people use it without really understanding that. Then they get stuck when they start trying to treat it like a traditional RDBMS datastore, which it is not.

Amplify "dumbs down" something that really should not be dumbed down. That's it's biggest problem and the reason I also stopped using Amplify some time ago.

> I think this article might bury the lede a bit:

When you read that quote carefully it doesn't say that Amazon employees get paid less. It's saying MAX pay at Walmart is $25/hr and MIN pay at Amazon is $18 an hour.

Apples and oranges. Meaningless clickbait.

This is for when the departmental budget has a little cash left at the end of the fiscal year and they need to spend it.

I found out while sitting in a hotel lobby at Abode's MAX conference in LA. Watching the news ripple through the tech crowd attending was something.

If OP has only one customer they do not work for themselves, they work for that customer and have a job - regardless of what they like to tell themselves.

I wasn't in the valley at the time but was part of a startup that lost our angel funding before it happened because the angel's funds were overcommitted already in failing startups.

My view has always been that during the dot com boom, companies were so short staffed that they would basically take anyone on, regardless of their technical skill, with the hopes of training them up to learn programming. Janitor, receptionist, your weird cousin Eddie who ate glue - all of them could get a tech job if they really wanted one.

When the bubble burst, lots of people lost jobs. Both skilled people and unskilled. This was a huge darwin moment for people who'd worked at startups. Lots of people went back to whatever they were doing pre-bubble. The better people typically found work, even if it took a little while to do so.

In my view, it really did serve as a healthy shake-out of talent in the long run. This very well may happen again soon...

> PSA: porting an existing application one-to-one to serverless almost never goes as expected.

Came here to post this and agree 100%. Moving to Serverless requires evaluating the entire stack, including the server side language choice, and how the client handles API calls.

Often a move to serverless is better accomplished gradually in stages than the quick "lift and shift" that AWS like to talk about so much. Sometimes you can simply plop your existing app down in Lambdas and it runs just fine, but this is the exception not the rule.

There is a long tradition in the US (World?) of blaming everything on "the younger generation". Don't you fret millenials, soon they will move on to whoever's next and you will be forgotten.

In the meantime, try not to be so sensitive about it okay? It's really nothing personal.

The list of sources used for "corroborating" information is interesting. It includes sources like tigerwoods.com