Hacker Newsnew | past | comments | ask | show | jobs | submit | jonathanrmumm's commentslogin

3. Young people who realize this dynamic and start their own companies because old people are less energetic toward picking up new tools / learning new tricks and run circles around them.


Remember my dad taking me here all the time and being amazed by aisles full of bins of random parts. Made you want to tinker.


Embeddings are a new jump to universality, like the alphabet or numbers. https://thebeginningofinfinity.xyz/Jump%20to%20Universality


If we're talking conscious thought, millions of simultaneously firing neurons to form words. If we're unconscious intelligence, it's closer to latent space. A lot of intelligence that can't be articulated.


(citation needed) It sounds fun and all, but we barely have any connection between human brain and llms as they exist today.


We need to reboot Bryan Cantrill's "Don't anthropomorphize the lawn mower" talk with a new edition titled "Don't anthropomorphize the internet document simulator"



Nice, right from the horse's mouth. Let me watch that.


There has never been a more fertile environment for motivated learners to do more with less, and yet we still have a bias as an industry to seek the more experienced hand versus the energetic one.


As the pure value of energy decreases, the value of judgement and taste increases.


Judgement and taste increases with energy spent—and from a company's perspective, usually you want it to grow in line with your own.


This is the real problem, possibly: the dev seniority pipeline dies without junior devs learning.

Also possibly, good would-be-junior-devs find something more productive to do.


They can, if people are growing. So many mid level engineers at my company spend their energy on the same year of experience.


The one thing they had was enthusiasm, but even the most committed and energetic junior hire cannot touch the productivity of AI on most of the work junior software devs are handed.

People are focused on absolute llm accuracy, but time-to-90%-there for AI vs junior dev is seconds to hours/days.


- Linus Torvalds wrote Linux at 21 - Steve Wozniak built Apple I at 25 - Palmer Luckey created Oculus VR at 20 - Vitalik Buterin designed Ethereum at 19 - Mark Zuckerberg coded Facebook at 19


And not one of them was hired as a junior dev.


They developed software as "juniors" in companies—we just don't belittle them by calling them "junior devs".


Bringing in No True Scotsman doesn’t save the argument.

These people were exceptional outcomes, where luck and hubris met sufficient competency. You cannot argue the general case from exceptions.


If we view the person we are looking to hire as a "junior dev", a "junior dev" is what you will get. But if you seek a young, competent software dev—one you might find.


Try to forget the mindset that you need an authority in order to learn. Better to pretend authorities do not exist.


Embeddings are a new jump to universality, like the alphabet or numbers. https://thebeginningofinfinity.xyz/Jump%20to%20Universality


Mind-blowing. In effect, among humans, what separates the civilized from the crude is the quest for universality among the civilized. To say it differently, thinking in terms of attaining universality is the mark of a civilized mind.

I made an episode to appreciate the book: https://podcasters.spotify.com/pod/show/podgenai/episodes/Th...


have it format in yaml instead of json, incomplete yaml is still valid yaml


good developer relations is less shotgun marketing and more proactive technical customer-support


why not just say "less is better?"


Because that's not the common, generally accepted term.


Because "Worse is Better" entered the lexicon circa 1991.

https://en.wikipedia.org/wiki/Worse_is_better


yes, why? seems like not that useful of a phrase if it needs an explanation with parenthesis in a wikipedia


The phrase was made famous in an influential essay[0] by Richard P. Gabriel, where he laments Lisp's relative failure to compete with Unix.

In Gabriel's opinion, Unix proved to follow the more adaptive design strategy in certain ways (in spite of his involvement with and admiration for Lisp), and the phrase "Worse is better" is meant to capture the essence of that advantageous strategy (as outlined in the essay).

The essay is worth reading and is a bit more elaborate than just saying "less is more", or "keep it simple, stupid".

[0] https://dreamsongs.com/WorseIsBetter.html


Ah so it’s more “if it’s not broken enough, don’t fix it”


Read the essays, they're excellent.


> it is better to start with a minimal creation and grow it as needed

yes, this is a much better explanation than the wikipedia


"Worse is better" comes from an ancient story where the Lisp folks were trying to design an elaborate system for resuming interrupted syscalls, and the UNIX folks just returned a "we fucked up" error to the caller instead. People take different lessons from this. Personally I feel like this is one of the earliest software forms of YAGNI: the (lack of) severity didn't merit the engineering effort to "fix" it. But, OP's interpretation is also valid.


It doesn't convey the same idea


What idea does "worse is better" convey to someone who hasn't heard of the phrase before?


then someone needs to update the wikipedia

> It refers to the argument that software quality does not necessarily increase with functionality: that there is a point where less functionality ("worse") is a preferable option ("better") in terms of practicality and usability.


"Worse" is not "less". It's about things like non-complete features, non-scalable architecture, and non-fully solved problems.

Besides, "less is better" is not a paradox.

There is another famous phrase that is "less is more". But it's a very different one (And "less" would clearly map into "not worse".)


Exactly. "Worse is better" makes zero sense.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: