- frank_nittiIn terms of demand, anecdotally-speaking I can certainly see this influencing some decisions when other circumstances permit. Many people I know are both excited for new and better games, and equally exited about running LLM/SD/etc models locally with Comfy, LM studio and the like
- Jenkins not looking so bad anymore..
- Hmm well I certainly inferred the same from their comment: it casts “big tech” as the victim of the government, because the latter forced as “overpriced and shitty solution”
It’s possible they’re not a capitalist and just extremely sympathetic to Apple and/or Google specifically, but that seems more of a stretch than what that commenter (to whom you’re replying) has inferred IMO
- Every single place I’ve stayed in Europe had no shower door, and nothing to prevent the water from spilling out. Occasionally I get lucky and the floor is constructed sufficiently concave so at least the water flows into the drain
- I love it! And yeah .NET Framework is still critical for some workloads, most notably C++/CLI and WCF for certain apps where deep win32 APIs make their net8.0+ alternatives too much of a headache :)
To temper my comment, the resistance I faced as the new guy brought in to modernize is natural for these engineers who knew their tools and systems well, in their defense. Eventually they warmed up from full pushback to friendly banter “Mr. Linux and command line over here” and accepted that running my little scripts helped address the confusion/frustration of Visual Studio disagreeing with Jenkins/GitHub Actions automations and runtime behavior in Kubernetes.
- If they’re in a team similar to some I’ve worked with, engineers are barely getting comfortable with the shift away from .NET Framework (!)
There are legions of developers for whom Visual Studio on Windows is the only place they have ever been comfortable. And upgrading between versions of .NET is a point-click exercise between the various UIs (Visual Studio Installer, “Get New Components or Features”, and the NuGet package manager)
The advent of .NET Core happened to coincide with initiatives to adapt:
* toward the cloud and away from IIS and Windows Server
* toward Git and away from TFS
* toward remote CI/CD and away from “drag my files into inetpub”
* toward SPAs and away from ASP.NET XAML programming (Blazor notwithstanding)
* toward a broader toolkit where the familiarity with OSS and open specs is advantageous, and away from Visual Studio as the center of the universe (though it still arguably reigns supreme in its class of IDEs)
Coming from the Linux/Docker world before going deep in .NET, I was both resented and leaned on heavily for these teams’ transitions. Most of my teammates had never read the contents of their .csproj or .sln files, or run a build command from a terminal and read its log output. They were annoyed by my requests to do so when helping them troubleshoot; some just rejected the idea outright (“there’s no need to look at VS internals here”, “we shouldn’t need to run DOS commands in today’s world, VS should hable this!”)
I can definitely sympathize with developers who were sold on what seemed like a promise that deep VS/IIS/etc knowledge would be the rock-solid foundation for business software for the rest of their careers. During the uprooting process, other promises like “netstandard2.0 will be forever for your core libraries and all future .NET runtimes!” end up with asterisks the following year.
I am 100% in agreement that .NET dev team is doing an amazing job, but it’s precisely because of their continued shakeups when they see major opportunities to improve it from the ground up, and probably the same reason that others feel wary of it
- Police that I’ve spoken to will readily confirm this. They consider profiling, not necessarily racial, an important part of patrolling. If they decide you look the part, they will find a way within several minutes/miles of watching.
- As a fellow former grocery store employee, I can agree about the “break up the monotony” concept from the narrow POV of the bored worker.
It is an inconvenience though, even if as insignificant as an eyesore for others, or the landscaper who may need to remove shopping carts from the planter to do their work.
You could apply similar logic to people who carelessly throw trash in the recycling bin or on a sidewalk where it’s someone else’s job to clean up after them. I’ve seen people go as far as to say they are graciously “providing a job” for someone else when they throw their refuse in the recycling bin.
The fact that the shopping carts are such an inconsequential thing to shrug off is what makes them a great litmus test — will you do the right thing simply because it’s the right thing to do, even when there is so little at stake
- Not to mention that, at least on the iOS app, the button to close an ad is in a totally different place than the rest of the UI screens, which is always in the top-left of the screen. A small “X” is placed in the middle-left of the ad image, to make you spend an extra second finding it, which I would assume they are happy to report as a user engagement metric to their advertisers.
- Oh definitely, many headaches untangling massive “variables.tf” files where the value is identical in 100% of the target environments, and would be nonsensical to change without corresponding changes in the infra config resources/modules as well.
My favorite are things where security policy mandates something like private networking and RBAC, and certain resources only have meaning in those contexts, for heavens sake why are we making their basic args like “enforce_tls” or “assign_public_ip” or “enable_rbac” into variable params for the user to figure out
- These are great and succinct, yours and your teammate’s.
I still find myself debating this internally, but one objective metric is how smoothly my longer PTOs go:
The only times I haven’t received a single emergency call were when I left teammates a a large and extremely specific set of shell scripts and/or executables that do exactly one thing. No configs, no args/opts (or ridiculously minimal), each named something like run-config-a-for-client-x-with-dataset-3.ps1 that took care of everything for one task I knew they’d need. Just double click this file when you get the new dataset, or clone/rename it and tweak line #8 if you need to run it for a new client, that kind of thing.
Looking inside the scripts/programs looks like the opposite of all of the DRY or any similar principles I’ve been taught (save for KISS and others similarly simplistic)
But the result speaks for itself. The further I go down that excessively basic path, the more people can get work done without me online, and I get to enjoy PTO. Anytime i make a slick flexible utility with pretty code and docs, I get the “any chance you could hop on?” text. Put the slick stuff in the core libraries and keep the executables dumb
- For me, it would be because the term AGI gets bandied about a lot more frequently in discussions involving Gen AI, as if that path takes us any closer to AGI than other threads in the AI field have.
- Great insight and advice I need to take - your description captures my current situation almost to a tee, better than I’ve been able to understand it for myself, so thank you.
In addition to what you described, in my case this engineer quickly recognizes other highly-effective and/or important people, and aggressively tries to build that reputation by privately messaging and even privately demoing work where the recipient has some stake in the outcome.
I would onboard him to a project, sharing all of my tools, key contacts and personal insights, e.g.
“our manager Smith is hinting that there is a big customer interested in X capability, which I’ve discussed with their power user Wilson and product owner Flores informally in recent demos. I think we could use Y approach and want to start prototyping if we get the go-ahead”
This engineer would start messaging Flores, Wilson and Smith privately and schedule calls about X excluding me and other core maintainers to push the thing forward, often proposing Y in his own words.
This strategy worked wonders for him in terms of upward movement. He is a diligent and extremely responsive to important people. But the strong engineers from whom he has effectively stolen credit, or even the opportunity to have a seat at the table in critical early discussions, obviously resent it.
His direct manager is lackadaisical and basically just gets bombarded by this engineer asking for frequent, long 1-1 calls where he shares “his” accomplishments and ideas. I’ve watched this play out in person (we are a remote-only team except for big project-related events) — his manager clearly trying to leave the event after it concluded, keys in hand and facing his car door, everyone else has said goodbye and given space, and this engineer keeps him there talking for no less than 10 more minutes.
I’ve never met someone so comically ambitious and overzealous to be seen as the MVP He was promoted in record time, much to the frustration of stronger and more critical maintainers.
I am baffled by the whole thing, and just laugh at this point. My most charitable interpretation of manager’s actions are that they do recognize the dynamic, and just don’t care because ultimately their job is slightly easier for the meantime. But if any 2+ of the critical core maintainers split in frustration, the whole thing will suffer, badly
ETA: it seems to me that remote-only teams are particularly susceptible to this kind of thing getting out of hand, because the capacity for secret communication is immensely greater
- Yes
https://youtube.com/shorts/nNfDr18C6H4?si=CKalCaG0DMUP3rZZ
This and my original comment apparently struck a nerve for some people, but I’m just sharing what I observe from the links I’ve included. I’d love to see some actual response to the content of these videos given Kirk’s apparent change of heart on Israel (especially if I’m off-base) as opposed to just downvotes with substance-free responses
- Even Charlie Kirk, of all people, was talking about this (ignore the clickbait video title): https://youtu.be/3wUq3t9f6ug?si=nV_NukcsjHZgj0MT
- Honest question - is NSFW just a code word for pornography now?
I had thought it would be anything that isn’t safe to open at work, including things with extreme profanity or gore, etc
- I would be more interested to see your response to the key point of their comment - that the US exemplified this on a large scale in recent history.
That would be more compelling than to simply claim to have a lot of knowledge of history
- I agree with your sentiment. But where I struggle is: to what degree do each of those ads “represent one less person who would have been paid” versus those that represent one additional person who would not be able to afford to advertise in that medium.
Of course that line of reasoning reduces similar to other automation / minimum wage / etc discussions
- Has there been a sufficient indication to conclude these weights will not (now or ever) be released?
- We might be talking about two different things. Yes, under normal circumstances the setup steps involve software that defaults to using telemetry -- though I'd be surprised if it's not possible anymore to achieve those in an air-gapped env using e.g. offline installers, zipped repos and wheel files, etc.
My comment was referring to runtime workloads having no telemetry (because I unplugged the internet)