608 karma · joined April 19, 2024
> There must be in-groups whom the law protects but does not bind, alongside out-groups whom the law binds but does not protect.
This administration has been playing a lot of games with "budgeted" vs. "delayed" vs. "actively being worked on" (or not). So this isn't really that different than the abrupt cancellations or delays or re-org'ing of funded and legislatively mandated work.
The main difference is the uncertainty. IMO anyone would be incredibly foolish to accept a deal from a random email with such limited info on the exact terms of what happens in edge cases like you describe: shutdown, budget shenanigans, actual official RIF, etc.
That's awesome. And, I think that's what a lot of people here are talking about: options.
If your customers largely wants sales calls and sales engineers, that's great. But don't ignore the (smaller) population that does prefer no-calls.
That's kind of begging the question. Part of the point of the thread here is that it seems B2B is leaving some money on the table by refusing to do deals with less interaction. For example, this CTO's comment [1].
A good comparison I think is AWS and other cloud offerings. Of course, past a certain spend, you will start getting calls and have the opportunity to negotiate better rates, SLA's, etc. But, you can just go and spend 5-6 figures per month without any human interaction.
Another good example I think is 5 figure (or maybe even 6 figure) equipment purchases. You can definitely go ham buying most professional equipment without having to talk to someone over the phone. Think servers, GPU's, storage, cameras, etc.
It'd be great if more services offered this.
Cars are similar I think. Sure maybe some people need help. But there's is huge demand for a one-click, no-negotiation car buying "experience" (or lack of experience rather).
My conspiracy theory is that this has more to do with Salespeople and established sales channels (dealers) not being able to understand this both because their job depends on it and because they are naturally people-persons. So it feels intuitive to them and they have trouble understanding/accepting that many other are not.
But also, if you want people to stop mocking "Open" AI, then maybe they should stop being such a mockable caricature of themselves.
[1] https://github.com/microsoft/graphrag/tree/main/graphrag/pro...
This makes a lot more sense to me than blackmail.
I'd quibble though that this overlooks that quite a lot (possibly even most) drug users are able to lead productive lives without having to resort to illegal activity to fund their drug use.
The other thing this doesn't cover is that there are many alcoholics that fall into the same trap. Though there again, most alcoholics are able to lead productive lives despite their addiction.
And through personal experience, I unfortunately know quite a few alcoholics that work in defense with various levels of clearance.
Yes, you need to drug test for clearance. But I'm saying that's a job I'm not applying to unless I have no other choice. It goes straight to the bottom of the pile for me.
Is this a Spelunky reference? If so, I love it.
This issue of "how can we ensure this code is under copyright terms XYZ" seems to have been popularly solved by CLA's. And thus a pall has been cast over the traditional open source dynamic, where there'd normally be no question that a fork with a license in the repo is obviously licensed under the same terms.
I've heard this on legal podcasts as well. Where lawyers spend like 30+ minutes talking about whether a license in the project root counts. To the traditional free software / open source movement, this seems really silly, because that's how software projects worked for almost the entire existence of free software / open source software until the last 5-ish years.
Right now, there is no actual downside for executives. Just less upside. Did they earn XX Million this year or XXX Million. Some tangible downside would be nice.
I mean, heck, why aren't they fired? And really, it's more then middle management where that'd make a huge difference. If bad performance led to actual shakeups in the entrenched middle management, we might actually see business practices change rather than continue on through the established fiefdoms and petty corporate politics.
Audit logging is definitely another must for me. I literally won't make an app without it. The app I'm working on now had a case where a PM promised up and down that edit history wasn't needed for a particular section, and lo-and-behold 2 years later it turns out that actually we do need the history.
It’s pretty tricky to get right and is very case by case in what it specifically means. But it’s been critical to handling edge cases.
For example, in 99% of cases, you can’t progress to stage X without doing Y. But in this case „I know what I’m doing”.
Though this puts a lot of pressure on downstream processes to handle missing data. Fortunately that hasn’t been an issue too much because validation grows and changes over time and must naturally deal with records that were created under prior validation when their state was originally valid.
With a Go project, I can leave it to sit for 3+ years and then pick it back up and add a feature without any issues. I've never had that with a Python project. (and this isn't even about the 2-to-3 situation, I just mean minor version to minor version and packages)
This helped me understand what role each ingredient and cooking step actually does. Similarly, they have great advice on efficiency so that cooking doesn't take as long or as much work.
It really helps me understand what they’re doing better. It short circuits a lot of bureaucracy. And it’s great when you can push out a change for someone an hour after they wanted it for simple things. So they know that you can make changes fast to address their problems.
And it’s just nice to get to know the users and be friendly. We get to chatting. And it just makes everyone more chill knowing that the developers care.
I also loved building my Prusa printer. That took much longer to build (like probably 5 hours for me). But it was really cool to learn all the parts and feel really comfortable with how it works.