your "physics" grounding is exactly why it feels so odd - software is by its nature anti-physicalist
math and logic are closer to a basis for software abstraction - but they were scary to business people so a "fake language" was invented atop them - you have "objects" that don't actually exist as objects, they are just "type based dispatch/selection mechanism for functions", "classes" that are firstly "producers of things and holders of common implementation" and only secondarily also work to "group together classes of objects"
I feel that is a bit of a false history. OOP was invented by people trying to simulate physical systems, e.g. Stroustup, the Simula people and their contemporaries not business people. Arguably it was popularized later by business people and enterprise Java developers. But that happened way later.
I do not think OOP ever really worked out well as can be evidenced by it no longer being as popular and people having almost entirely abandoned "Cat > Animal > Object" inheritance hierarchies.
This is also a bit of a false history. OOP was squarely invented with Smalltalk. The term was literally conceived for Smalltalk to describe its unique (at the time) programming model. While objects most certainly predate Smalltalk, it was Smalltalk that first started exploring how objects could be oriented.
OOP didn't really take off either, but mostly because it is hard to optimize and impossible to type.
what's the modern "absolute beginner's guide to async in Rust" - ideally something dense that can bring someone motivated from beginner to expert in ~1 week of intense hacking on it?
add async keyword to functions
add .await when calling them
use tokio in your main function (easy to look up)
use the async recursion crate if you need to use recursion but don't want to box everything
There are some bonuses like calling functions in parallel, but there you go.
can't for the love of dog parse the meaning of this - what do you mean? a callback that is async passed to a sync api? you refer to the complexity of sync<->async bridging? ...or?
just share the damn thing, someone may have something for you ;)
...I've kind of rarely seen these ppl complaining about work actually sharing their resume or a condensed description of their skills, knowledge and experience
ok, f googled it and found it: ~"entry-level/junior sysadmin and cyber"
so, a path could be picked from what you know:
1. devops/sre - really hard to get above entry-level without real experience and you _will_ be competing head on with AI ...ouch
2. cyber - same with whitehat as with devops/sre ...basically go full red-team / blackhat / offesinve for a while, the get certs and portofilio, then job in "real cyber" ...BUT ppl that do this tend to have a "very specially broken brain", so if you haven't done this already you're probably not one of them [probably for the best]
...but they're probably all bad, so better DO SOMETHING ELSE ENTIRELY:
...gtfo of software, you're likely not gonna become an "agents hearder" with skillset, mentality and experience - in the US probably going full on on agriculture [recent US protectionism and isolationism will give you decent levels and shield for globalized markets], learning some minimal hardware tinkering to automate drones and later manage android workers, software for planning farming automation etc... hire hands for physical labour and BUILD AND MANAGE A FARM or something like that (maybe farm + restaurant or smth else form tourism / hospitality)
All of the three sectors you've mentioned are not in a good place right now. Probably much less stressful to be an unemployed programmer than trying to make a hobby-scale farm profitable with soaring fuel and fertilizer prices, along with a labor force that is fleeing.
E: Farm automation probably has some juice though, regardless of how close the androids I keep seeing in demos actually are.
bc software engineering learning is 99% BOTTOM-UP...
and that's bc SE education FAILED BADLY... almost nothing of what's useful is thought in schools and nothing of what's thought is useful
instead of FIXING education and theory, software engineering marched on forcefully without it
now we need to go back and properly fix education, because an intern should absolutely be required to have the "advanced" skills that we imagine in our deluded minds that only "10+ ys of industry experience" should confer, and that are absolutely required to be even a junior AI-augmented SE
SE/CS education should be rethought from scratch to distill, purify, and teach in 3ys max the concepts that used to be acquired through 10-30ys of experience - it 100% CAN be done, and we should wake tf up and DO IT instead of complaining about it - "advanced enterprise systems" architecture require nothing more than mid-highschool math and can be thought on symulated systems in sem 1 of year 1, it's just some of the "teachers" would have to actually put in the 80hrs-weeks of work to do it in due time
> going into every interaction thinking about which parts of oneself to dial down
what if (a) I hate leading questions, (b) by default only smile when bad/tragic things happen (eg "train crash leaves 100 dead and maimed"), (c) I'm quite bad at listening bc if you don't say interesting things often/densely enough my mind adhd-s away, and (d) interrupting is second-nature to me?
...advice may be good, but for some of us it's like 99% of ourselves that we need to dial down in order to carry on a successful interaction - it works, but takes a hell lot of energy
You seem to have a lot of limiting thoughts about yourself. Other people do those kinds of things but just don’t mind and don’t think that they are a bother to others.
You’re allowed to be weird. Weird people make the best conversation because you don’t know where they’re gonna go
Yes, you and I are making the same point :-) There's lots of useful advice out there about how to be a better conversationalist but it's exhausting for those of us who have to constantly think about it, and disheartening when we get it wrong despite all the effort.
can't we just have tabs + tiling (either tiles in tabs, or tabs in tiles, both can work), and call it a day?
that's all I need from browsing today
reply