Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The use of “full-stack” was the first thing I noticed. Everyone, please stop using that term. I’m pretty sure, with a high degree of certainty, you don’t know what it means. If you do, there’s a merit badge waiting for you. And can we please stop using “hallucinations” to describe output. Yes, it may look like your tool dropped acid, but that’s not what it is.


Rob Pike once said that he was "full-stack": when he worked on Voyager, he understood the system from quantum mechanics to flight software (https://hachyderm.io/@robpike/109763603394772405)


No joke: The guy that coined the term is the same guy that made the merit badge. Enjoy looking that one up.


full-stack means the ic can take any ticket. do the details beyond that matter?


Well, quantity has a quality all its own. Extending the sprint to wait for the person to complete their PhD as part of the "research" part of the ticket would not quite be Scrum.


Buy the ticket, take the ride…


first you have to be told what you’re buying next.

(before that you were given the chance to object to the estimate, but not to change it.)


No sympathy for the Devil, keep that in mind.


I now think of the "stack" of a modern business as starting with physics and ending with making someone happy (unless you are Oracle). Full-stack engineers should then know how to connect physics to peoples' happiness.


> can we please stop using “hallucinations” to describe output.

Right. A better word is confabulation.

I.e. pseudomemories, a replacement of a gap in information with false information that is not recognized as such.




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

Search: