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

Built this for a bit of fun over the break. It pulls my (extremely not up-to-date) record collection from discogs and displays them as a three.js render. In case you're wondering, the stickers on the sleeves without sleeve art are how I tag blank sleeves with genres (green = electronic) in real life, so replicated it in the render.


I immediately stopped reading after I saw the format. Absolutely hate this linkedin style 'everything is deep' posting. It's crap


This was a great read. I used to work at RA as a dev, I always look back and wish I did more with the data I had access too!


I'm a sales engineer and demoing is one of the core parts of the job. I think this is applicable if it's an internal demo or a demo to a large audience, i.e a conference where you have a very fixed window of time to present.

I would never recommend doing this in a sales context though, where you're selling to prospects. Mainly because it gives you no flexibility to pivot and adjust the content based on what they're interested in, and also because it gives off the impression you don't have a lot of faith in your product to perform live.

I'd still 100% recommend having pre-recorded backups however. I was once doing a demo to our largest customer in region and the second we joined the call our core product had a SEV0. I was very relieved to have something to show while the engineers fixed the issue.


This is actually pretty big in Sydney, and I was inspired by a few people I'd met that were in hardcore / punk bands that were all straight edge!


Have heard of the Sinclair Method having pretty overwhelming success, however I haven't seen it in use much in Australia yet.


I definitely noticed this with a lot of people I worked with in engineering. They were quite shy and a bit hard to crack, but once they had a drink or two at a work event they were very sociable and easy to talk to. And outside of these situations they never really drank. So I think for them, alcohol was never really an issue.


This pretty closely describes how/why I usually drink as a dev.

While sober I can function socially more than well enough to get along in the day to day without issue, but it’s much much smoother if I’ve had some alcohol (but not too much).

I also tend to focus more squarely on my conversation partner when I’m buzzed, whereas sober my head is all over the place, plus I don’t get bored with the conversation or lose energy to converse as easily.

Since beginning to work from home I’ve had very little to drink, averaging 0-2 beers per month. It’s really a social thing.


Humanity has been bonding over beer for thousands of years - I'd guess it's adaptive and selected for.

The cultural signaling of whether it's cool to give it up or not just comes in waves imo (outside of people with more serious drinking issues). Right now it's cool to say you don't drink so there's lots of these blog posts, same category as people that tell you 'they don't even have a TV'. It's not that interesting, but generates a lot of commentary from people in both directions and I think it's mostly some form of social status thing.

I've noticed a similar thing with young people thinking it's cool to be religious after a swing for a bit in the other direction. There's always some points you can get for doing the less common thing in certain circles.


I'm glad you got something out of reading it! I was in a very similar situation as you where everything sobriety related I read made it out that quitting would turn me into the ubermensch overnight.


Can I ask what sort of front-end frameworks/tools you use that you also condemn?


Most of them are merely abstraction layers for capabilities the browsers already provide. Rarely do they offer anything more. The big selling point is that they help organize the logic in a declarative way or automate a bunch of tiresome tasks that wouldn’t be there in the first place had you not used a mountain of tooling.

There are only 2 APIs in the browser: DOM and the web APIs. As far as writing cohesive logic that does wonderful things that’s on you. Most JS developers would rather it not be on them and instead adopt an Invented Here Syndrome mentality. The fear of writing any original code is very real.

https://en.m.wikipedia.org/wiki/Invented_here


Yeah agreed. This whole thing reads more like someone trying to find a reason to drag Buttigieg's name and deciding to use his past at the big bad McKinsey.


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

Search: