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

"Laid off" may be more appropriate than "fired", but in essence, removing the need for costly labor is often the main "value" of any technology. Society as a whole comes out ahead from it, I mean for all the ice transporters and merchants put out of a job by electric refrigeration, and all the sailors put out of a job by modern cargo ships I think we're better off for it. But at the individual level it does make one uneasy about the prospects of individuals affected by it. My personal conclusion is that people have a personal duty to anticipate and adapt to change, society might give them some help along the way but it doesn't owe them that their way of life will be maintained forever.

This is putting the apple cart before the horse.

Economy should be a tool for the society and to benefit everyone. Instead it's becoming more and more a playground for the rich to extract wealth and the proletariats have only purpose to serve the bourgeois lest they be discarded to the outskirts of the economy and often to the literal slums of the society while their peers shout "you're just not working hard enough".


Very true. We waste alot of valuable labor on “software engineering” that is grossly inefficient. Capital gets allocated to these so called startups that are incredibly inefficient.

This says a lot as relating to the rise of AI and the fear of job loss. There's going to be displacement in areas we can't predict, but overall it might very well just lead to leveling up the entire workforce.

> it might very well just lead to leveling up the entire workforce.

How could that possibly work?

At some point I could see white collar work trending down fast, in a way that radically increased the value of blue color work. Software gets cheaper much faster than hardware.

But then the innovation and investments go into smart hardware, and robotics effectiveness/cost goes up.

If you can see a path where AI isn't a one-generational transition to most human (economic) obsolescence, I would certainly be interested in the principle or mechanism you see.


Craftsmen will have a resurgence, that's probably a 'leveling up' in terms of resilience against AI takeover. There's just no way of automating quite a few of the physically effective crafts.

So the rich who can afford craftsmen will get richer, spend more on their multiple houses, perhaps. But that's literal crumbs, one or two jobs out of tens of thousands. There's no significant "leveling up" there at the societal levels of job destruction we're talking about.

TFA mentions that some sequencers at the time did not support generating at more than one decimal place

It's unlikely (but not impossible) that Logic would take 12345 input and insert the decimal automatically. The point was that adding the decimal point may not be necessary, especially in software with specific constraints; all sequencers I've come across have BPM ranges (typically 30-300) it's not too much of a stretch to think they could try to "intelligently" convert something that out of range rather than just clamping.

That looks like it's trying to do too much and too little. Too smart for a dumb phone, too limited for a smart phone. The hard keyboard feels antediluvian now that we have swipe or voice recognition typing with relatively acceptable accuracy, or for typing in multiple languages.

Meanwhile the "other" French insect farming startup seems to be doing fine (Innovafeed)

They should stick to snails.

This is informative for an indie audio podcast. I wonder how the economics and scale change for podcasts published by studios like Audible or even smaller ones like Pushkin


Did this change? I stopped reading the print version for lack of time a few years back, and there was definitely some full-page and margin advertising throughout the paper. I recall some of it being clearly directed at much wealthier customers than I was.


The placements and counts tends to vary issue to issue, but in general is much lower volume than many publications. But agreed, the ads do tend to be almost comically high end (for me)


You might also need different systems for low-cardinality, low-latency production monitoring (where you want to throw alerts quickly and high cardinality fields would just get in the way), and medium to long term logging with wide events.

Also if you're going to log wide events, for the sake of the person querying them after you, please don't let your schema be an ad hoc JSON dict of dicts, put some thought into the schema structure (and better have a logging system that enforces the schema).


When these companies were founded, they had nowhere near the scale and resources in the hands of the current set of folks. Zuckerberg at 28 was riding a bike and this is a rocketship (pointed up or down, is not clear)


In my experience, discernment and good judgment. The "generating ideas" capabilities is good. The text summarization capabilities are great. However when it comes to making reasoned choices, it seems like it's losing all abilities, and even worse it will sound grossly overconfident or sycophantic or both.


There are really two kinds of "small bugs".

1) Things that have existed in your product for decades and haven't been major strategic issues.

2) Things that arose recently in the wake of launches. This can be because it's hard to fix every corner case, or because of individuals throwing sloppy code over the wall to look like they "ship fast".

I try to hold the team to fix bugs (2) quickly while their memory is fresh as it points to unwanted regressions.

The bugs in (1) are more interesting. It's a bit sad that teams kinda have to "sneak that work in" with fixit weeks. I have known of products large enough to be able to A/B test the effects of a quarter's worth of "small fixes", and finding significant gains in key product metrics. That changed management's attitude with respect to "small fixes" - when you have a ton of them, they can produce meaningful impact worthy of strategic consideration, not just a week of giving the dev team free rein to scratch their itch.


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

Search: