Disruption happens when firms are disincentivized to switch to the new thing or address the new customer because the current state of it is bad, the margins are low. Intel missed out on mobile because their existing business was so excellent and making phone chips seemed beneath them.

The funny thing is that these firms are being completely rational. Why leave behind high margins and your excellent full-featured product for this half-working new paradigm?

But then eventually, the new thing becomes good enough and overtakes the old one. Going back to the Intel example, they felt this acutely when Apple switched their desktops to ARM.

For now, Claude Code works. It's already good enough. But unless we've plateaued on AI progress, it'll surpass hand crafted equivalents on most metrics.

Coding, writing, summarizing, translating, data analysis, customer support, test generation.

They're in the app stores. Apple's review times are skyrocketing at the moment due to the influx of new apps.

This is a worthy tradeoff! Phones are bigger than ever and scrolling is incredibly simple.

Comments URL: https://news.ycombinator.com/item?id=42984706

Points: 22

# Comments: 5

I intended to learn back-end development before applying for jobs, but I've heard that nobody hires junior full stack developers.

Is this true in your experience? Should I learn any back-end, just get really good at React, or learn some other web technology? Any other advice re: getting my first dev job would be hugely appreciated.

Thanks in advance!

Comments URL: https://news.ycombinator.com/item?id=31895610

Points: 2

# Comments: 0

I'd love to try your recipe but I seem to be allergic to avocado and would not have a fun time.

I'm considering going in the direction of full stack development, so your feature suggestions could be great ways to learn backend.

> In case you were interested, there's a section devoted to that in RFC 3548: https://datatracker.ietf.org/doc/html/rfc3548#section-4 with the tl;dr of `s/[+]/-/; s/[/]/_/` and then omitting the trailing "=" characters and just padding the incoming b64 since (AFAIK) one can add as many "=" as they'd like and it'll just ignore extra ones

Thanks! I'll check this out.

> Depending on your interoperability interests, you can shave a bit of text out of it by shortening the JSON key names `"i"`, `"a"`, `"n"`, and then also `.filter(Boolean)` to nuke those two trailing empty strings

This is a good idea. I might already be filtering those empty strings but I'll have to check.

Here's my personal recipe [1].

If you take a look at that URL, you'll see it's quite long. I wanted to be able to share recipes, but I don't have any backend knowledge. I had to get creative and store the object representing the recipe in an object encoded in Base64. This presented some character escaping issues, but those were manageable.

I don't expect this project to change the world. I just wanted a way to practice my newfound React skills and share some smoothie recipes. If you give this a try, please share your recipe!

Thanks for your time!

[0] https://github.com/somewhatJustin/smoothie-stack/

[1] https://mysmoothiestack.com/?share=eyJpbmdyZWRpZW50cyI6WyJGc...

Comments URL: https://news.ycombinator.com/item?id=31574484

Points: 17

# Comments: 17

Comments URL: https://news.ycombinator.com/item?id=10236036

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=8294795

Points: 3

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=8158558

Points: 3

# Comments: 0