CactusOnFire

Most of numpy executes in C.

This is definitely the "software engineer" way of conceptualizing and solving the problem. You have discrete limitations, you optimize around them.

This is clearly not "working at intended" though and I'd like to believe everyone knows that, including the people building this system.

Far from an expert in Go or Rust, but I think the use-case for Go is you need to do something very by-the-numbers and you want it to be easy to maintain and performant.

Once you start reaching for more off-the-shelf solutions, you hit diminishing returns with it as a language.

In defense of the AI, that's about as good as the average player (and the average players is pretty skilled).

AI is bad at Audio. AI can do MIDI fine.

I mostly hear this word in the context of the Romans, but I thought that it was a term for facial hair- implying those external to the "civilized" empire had a tendency for ragged and long facial hair.

Hence the term 'barber' for a person that cuts said facial hair.

In general though, hasn't it been understudied?

You lost me here.

My gut feeling from reading the article and this thread has been that the monkeys should have been better taken care of. But the idea that every human advancement will only result in a win for the capitalist hellscape is some blackpill bullshit.

There are people who are trapped inside their own bodies due to neurological disabilities. Even if neuro-interfacing technology is used to huck consumer convenience devices, there are likely positive impacts on devices used to help these people. I don't really care about the 90% of people who are lining up to buy the neurolink equivalent of an iphone. I care about what those implications have for a disabled minority, as do many other people here who are commenting.

You don't have to feel like the trade-off is worth it, but if you aren't going to acknowledge that maybe technological process presents opportunities to help people, than you are being willfully ignorant.

If I recall correctly, "Working software over comprehensive documentation" is part of the Agile Manifesto.

I have seen this transformed into "We don't need documentation, just work on a new feature".

Got my foot in the door doing an after-school program teaching kids to code.

I leveraged that to get a teaching assistant job at a bootcamp for adult professionals.

I networked my arse off at the teaching assistant job until experienced programmers (such as instructors) realized I knew my stuff but was underemployed. I got a couple of side gigs doing BI Analytics that way.

After doing this, I had a tough set of interviews for my first full-time role. Every failed interview taught me about my weaknesses and blindspots, and I learned from them. I opted to get stronger at system design, stats & ML algorithms, though I feel like grinding leetcode could have been another approach at this point.

Because I had a wide set of marketable skills within data-oriented work, an analytics consulting firm took a liking to me. I had versatility for billable projects, and I got a bunch of tech certifications in AWS/etc. This role would be describable as 'Analytics Engineering'.

They overworked me for a little while, then my next role was a Data Scientist role that was on my own terms.

I don't want to make it sound like I could just jump in no problemo. I had to think strategically about how to climb each rung of the ladder. But I am now at a point where I have the experience needed to be a senior. While some companies might turn me down for not having a piece of paper, there are enough who actively want me that I am sitting pretty with my career.

I'm a Data Scientist who builds ML models. My bachelor's is in psychology, I just studied and learned how these algorithms work.

I've been on team FF since the switch from IE like 20 years ago- I agree sometimes there is additional jank, but I also want to add that it is rare enough that it's been a non-issue 99.9% of the time.

Even then, I expect some of it is the fact I use an obscene number of plug-ins to break most social media sites (to prevent overuse).

I watched this video earlier today, and had previously seen his video criticizing VPN services.

The video he was commenting on was about how "tradition" has no place in business, and then segued into why he believed a service like Nord VPN can be valuable.

The tounge-in-cheek segue was a reference to his previous video. I still believe that everything in that video rings true, but despite effectively "burning the bridge" with NordVPN, he ultimately found an effective use for the service, which was getting around region-bans and language-locks when using the internet abroad.

His willingness to endorse them wasn't inconsistent with his previous video- and he has said nothing contradictory. Rather than emphasizing this as a means of security, though, he emphasized it as a way to spoofing IP addresses for services that require you to be in a specific region- which for some people, might be worth the price-tag.

The reason why doctors have to jump through so many hoops is that the stakes are higher for failure.

While there are times where a piece of code failure or poorly worded instructions can cause injury to others, those are exceptions to the rule. Generally speaking- the cost of failure for writing and software is lower than it is medicine, and it makes sense not to gatekeep these industries behind theory, and rather just let results speak for themselves.

To hop on the maintainability point: The same is true for "High-code" solutions. If you want the ticket done quick and dirty, it'll be done in a quarter of the time. But good luck ever iterating on it with additional features.

I dated someone who had it- was beaten heavily during their childhood formative years, and told me that the separation of identities was a means of coping.

It seemed like an extreme emotional compartmentalization which left them with a fractured sense of self.

Some people might say that they could have just been pulling an elaborate hoax on me from a year and a half. But the amount of acting it would have required just to convince me of this without any real reward would have been a sign of even greater emotional problems than even the different personalities.

When I saw "Killed by google" I came out of it with a general sentiment about how google can't commit to a specific roadmap.

After seeing this site and then the comments here, I am coming out of this with the general sentiment that Microsoft is genuinely thoughtful about addressing end-of-life products.

They already made an MMO about Colonization. I think it has middle of the road reviews.

It's a differentiator between junior and senior because senior people need to make "the call" on using a technology, juniors don't.

There's a couple of other heuristics for whether or not something is worth using on a project (like complexity of learning, and context within a larger stack), but suffice to say it's about looking past a specific problem and on to subsequent problems down the line.

You're right. Fundamentally, there is no unbiased search engine. Ranking results by definition innately creates a bias.

(To be a pedant on my own post: I guess you could do a search engine that collates all search results relating to a keyword and then just shows you a random one first, but I doubt that's what the people want).

Use linux?

My next PC I am making the switch.

I have always figured the appeal of Haskell, Clojure, et al., is to transpile your task and turn any software problem into your language of choice.

My usual experience is that the top rated post is either insightful or a chuckle, but if you delve into the child comments from that particular post, or any more than a couple down, and it is an outright flame war over something trivial.

I don't want to claim I am an expert on different programming languages. I really wanted to supplant my JS use-cases with Elm, but the ecosystem is too closed for proper collaboration.

The biggest restriction on adoption is that the language is a gatekeeped brainchild of limited number of devs. They are inclined to build the language around use cases they want, instead of what people who use their language want.

They have effectively closed the gate to having other talented FOSS devs supercharge this language with features that allow it to run circles around other languages currently in production systems (mainly JS)

It's their right to do so if they wish, but it means that I can't consider this language in any serious capacity. It means the language lacks flexibility and reactivity to changing circumstances, and while it describes having a default library without extendible ecosystems as a "feature, not a bug", they've essentially put a ceiling on what is practical with their language in doing so.

I really wanted to like this language, but the more I learned about it, the more I felt disappointed over what could have been.

I agree entirely- and I try to do an "emotional audit" on how I'm feeling while playing a game.

I know exactly what you mean by that dopamine grind sensation, and when I sense that being present (and no joy), I will either uninstall and stop playing the game, or take a step back and reassess my relationship with the game.

I agree with your thesis, and I dislike the direction the gaming industry at large is taking.

At the same time, it's hard to see where lines are drawn. The only thing that really separates 'Engagement' from 'grinding' is whether or not you enjoy doing it.

While I take a lot of time in considering what games are worth my time, and have a positive "feedback loop" that will leave me feeling satisfied rather than burnt out, I also have to ask myself what "genuine play" really does mean. We can point out the behavioural strategies devs use for reinforcing more play-time, but outside of the question of perverse incentives like NFT's, paid lootboxes and pay2win microtransactions, a game needs to feel rewarding in order to be played. Some just have this reward cycle more ouvert than others.

Question for the experts in the comments:

I'm playing around more with deep learning as of late. Are the same technical specifications one would look for in a 'miner-friendly' GPU the same ones I'd look for in a GPU for Neural-net computations?

While Azure companies do tend to skew "larger enterprise", I don't think it's fair to say they are lower paying. If anything, more Azure-related jobs I have seen a higher-price point on than AWS jobs (in my local sphere). I think this is because Azure has higher demand than supply, and people are less likely to choose it as their primary cloud right out the gate.

It's also worth noting that a lot of consulting companies focus on Azure. This is because of perverse incentives, but still worth noting.

As an ADHD dev, the adoption of WFH at most companies has been a godsend. I cannot work in an office environment, and usually work in small 'bursts' of productivity over a day, where I do a day's worth of coding.

Not being watched takes the stress off of me to look like I'm doing something important.

Not quite as big of an offender, but when I was looking up "Nice Restaurants" with google maps fixed on my city, it instead started looking up Restaurants in Nice, France.