Link to the YAML spec, for the (very) brave: https://yaml.org/spec/1.2.2/
Link to the YAML spec, for the (very) brave: https://yaml.org/spec/1.2.2/
I honestly find it worrying that someone would think it’s some sort of deeply ingrained human trait when it’s clearly not culturally universal (eg. small hunter-gatherer tribes wouldn’t exist otherwise) and not present through all of history.
I think “growth” is a strong signal for people to put faith and trust into something. And that these emotions have influenced our behaviour for a long time.
Why did the Roman empire keep expanding? What made them want more? I’m not a historian nor an anthropologist (far from either!). But this feels like “line go up” behaviour. What would it mean for those in power to communicate that some part of the empire was receding? Even if, overall, the empire was objectivetly huge relative to other organised groups?
One thing I think about is there could be eroding confidence and trust of those in power by colleagues and the general population. If people lose faith, the powerful lose power; they lose ability to influence behaviour. Growth is obsessed over because it’s a means to capture influence over the means of production (and capture profit).
The line has to go up because the current economic system demands it has to go up
What about outside of economics? Even metrics on https://fedidb.org: shrinking numbers are coloured red. Growing numbers green. Green = good, red = bad.
Another thought. The other day I was at a cricket match. Grand final. Because the home team was losing, the stadium started to empty. It wasn’t about enjoying the individual balls/plays. Supporters were not satisfied with coming second (an amazing achievement, much “profit”!), it needed to be more.
To stretch this shitty metaphor further, when the supporters (investors?) lost confidence in their ability to deliver more, they just abandoned the entire match (enterprise?) altogether!
Again: I’m not stating anything here as fact. I’m just absolutely dumbfounded as to why “line go up” is, as you say, such an obsession. I hear you when you say that it’s a consequence of how the modern economy works. That makes sense. I guess I wonder what would happen if we snapped our fingers and we could start again. I wonder what the economy system would look like. Would we still be obsessed with growth?
Growth might be impossible, but a steady and “boring” amount of profit should still be possible selling plain-ole-dishwashers. Yet … for some reason, we don’t see that.
God yes this bothers and fascinates me.
Instead companies throw everything into growth and we get the retarded bluetooth enabled dishwasher problem everywhere, and I’d like toknow more about why.
I think it’s alluded to in the article:
They found a way to make consumers spend more money on dishwashing. The line goes up, for one more year. But it’s not enough. It has to go up every year.
Digging deeper: why must the line go up? Pesonally I see it as a deeply emotional, human thing.
When you read those annual financial reports from big companies, they will do anything to make sure things look rosy. Bullshit terms like “negative growth” are used because “loss” or “shrink” sound bad. So what if it sounds bad?
Confidence. Trust. It’s emotional. These are deep in our psyche. It’s how governments get elected, contracts are won, and investments are made. It’s what makes us human. If that line goes down… will it go back up? What’s going to happen? Alarm bells! Uncertaintly. Anxiety. People abandon you. Money, power, influence fades. You could find yourself replaced by the up-and-coming who “show promise”.
Our social emotional species has hundreds of thousands of years (millions?) of years of this stuff hardwired into us. Trust let us cooperate beyond our own individual or family interests. Would we be human otherwise? (I found the article Behavioural Modernity interesting).
Not sure it’s capitalism per se. Perhaps rampant waste. Criticism of capitalism could include monopoly formation; massive tech companies buy small ones (obtain more capital = more control over production = more profit).
There’s despair over everyone, big & small, resolving the same recreated problems. Kelley doesn’t talk about breaking Microsoft up (i.e. redistributing their capital). He implies he’d be ok for Microsoft to maintain its market position if it just fixed some damn bugs.
The art of turning a 500-line text file into a 50MB tarball. Welcome to the future :(
Here’s the article’s source: https://www3.weforum.org/docs/WEF_Future_of_Jobs_2023.pdf
That report’s data is a survey they sent out to companies. Quantising “so… what do you think is gonna happen?” seems… shonky?
Hm. Some views from other Lemmy instances…
some Australian one: https://aussie.zone/post/6544997
some Dutch one: https://feddit.nl/post/10144806
Big ol’ lemmy.world: https://lemmy.world/post/11512187
Mastodon:
Seems… OK…? Apart from lemmy.world (but that’s running a previous release of Lemmy).
PS from Mastodon (hachyderm.io): https://hachyderm.io/@[email protected]/111866487723645951
No replies or anything because nobody subscribed to mechkeyboards from hachyderm.io. I just subscribed, though :)
If I remember rightly, the backend update takes a long time as the database needs to do a particularly slow schema update. https://old.lemmy.sdf.org seems to still be ok.
Looks like there’s a fix incoming: https://github.com/LemmyNet/lemmy/issues/4288#issuecomment-1878442186
FYI, on lemm.ee I have been testing 0.19.1 patched with the #4330 changes by @phiresky for the past week and have noticed no further issues with outgoing federation, so I think this issue will be resolved with the next release
That patch has been applied (https://github.com/LemmyNet/lemmy/pull/4330) so now I guess we’re waiting for a release to be cut. Fingers crossed.
Even with (more) UX engineers, it was incredibly difficult to get any development done. When I was in this space, management and contractors were incredibly entrenched playing political games to grow teams even bigger to get more funding. There was nobody with any authority using the thing end-to-end saying “this sucks”.
I worked for a German car company for a little bit, in a team responsible for a similar system: https://www.srcbeat.com/2023/08/sbt/
Unfortunately for those who have those values, not all paid positions involve acting on those values.
Random brain dump incoming…
Most businesses pay money to solve problems so they can make more money. You can solve their problems - but not in the way that you may be thinking.
This is a generalisation that is not strictly true, but I say it to illustrate a different way of thinking: Businesses do not undertake penetration testing because they want more secure software. They do pentesting so they can stay in business in the face of compliance and bad actors.
To find a job, you want to start learning what people pay for. People pay contractors to come in and fix things, then leave again (politically easier, sometimes cheaper). People pay sotfware developers to develop features (to sell more stuff).
Start looking up job titles and see which ones interest you (DevOps, frontend dev, backend dev, embedded…). Don’t get too stuck on the titles themselves. It’s just to narrow down what kinds of business problems you find interesting.
Other random questions:
Once you’re deep in the belly of the beast, you’ll find ways to exercise those values. It’s hard to know in advance what this will look like.
Ah yes! That is a great trick that kept me going doing software dev professionally.
Instead of trying to get the system I was working with to interact correctly with some shit enterprise system, I would find common protocols (or related protocols) and implement that well. Then I would discover more specifically where the shit enterprise system was behaving badly, and point to something politically neutral (like an IETF RFC) to help get us out of a rut.
It made debugging so much easier. Those specifications and open-source implementations have had much more engineering talent put in them than what I was usually dealing with.
Oh there is absolutely zero disappointment.
Years ago I wanted to learn how OpenBSD worked. Some people said to me “ah you want to get into programming at OS level? I was a bit disappointed with Go. But don’t learn C, learn Rust; Rust is the future there”. So as a total novice I looked at all 3 on the page. My impressions were: Go looks easy, C looks a bit harder, Rust looks… way too advanced for a beginner like me.
Later when I heard of Zig I started reading and it looked a bit more like what I expected a “future C” to look like.
I wish I had more time and skills to do work in C, Rust and Zig. I’m a Go programmer by trade.
Would you say Go is popular enough to be called mainstream?
Zig is what I thought Rust would be like when I first heard of Rust. I’d love to try Zig for some hobby things but can’t get it running on OpenBSD (yet!).
I am consistently surprised by what companies are willing to pay to not worry about capacity. Incredible DataDog bills, for example, because they didn’t want to think about how many application metrics to store; “just keep it all!”. And boy do they happily pay for it!
Ok I’m starting to understand where you’re coming from now! It sounds like the leaders are happy for humans to do the work of increasing capacity on-demand rather than tackle the engineering challenges in handling workload spikes. The priority is to appease customers who are from well-known, “impressive”, well-paying (maybe not?) companies. Does that sound sorta right?
Inform and throttle. Think about how your own computer works. If storage reaches its max capacity, you get a signal back saying “filesystem full” (or whatever), not “internal storage error”. If the CPU gets busy, it doesn’t crash; things start slowing down, queued up, prioritised (and many other complicated mechanisms I’m not across!).
You could borrow those ideas, come up with a way to implement the behaviour in your systems, then present them to whoever could allocate the time & money.
Another approach is try to get a small, resource-constrained version of the system running and hammer it by loading heaps of data like those customers do. How does it behave? What are the fatal errors and what can we deal with later?
I feel this is a bit of a moot point from the White House. Memory-safe languages have been around for decades. I feel like the amount of C/C++ out there isn’t so much that people think having dangerous stuff around is good, but more that nobody really wants to pay to change it.