I would recommend trying out an active activity in your community that seems to be pretty popular. Not only will the physical activity be beneficial in physical and mental ways, but the communities are usually pretty welcoming to newcomers. I've met some great people via pickle ball, tennis, table tennis, jiu jitsu, and rock climbing gyms.

Interesting proposal, but I think it would take a good size of money. Maybe 50% escrow of first year salary?

Yeah something like that. A breakup fee between the job board company and the hiring company: “if you don’t hire someone within 90 days we keep half of the salary.” But there’s not much incentive for the hiring side to do this!

They'll find one way or another to laugh all the way to the bank, that is for sure.

People want to be deceived.

What's the potential that this puts things on even shakier ground? I'm sure the fallout wont really effect their bottom line that much in the end, but if it did - wouldn't making the US Gov't their largest acct make them more susceptible to doing everything they said?

I'm guessing they probably would regardless of how this played out, though.

~100%.

LinkedIn has a wild past. I'm surprised that it seems like no one remembers. Scanning users e-mail inboxes, creating fake users, etc.

It's all documented on Wikipedia too: https://en.wikipedia.org/wiki/LinkedIn#Criticism_and_controv...

IBM has cut ~8,000 jobs in the past year or so.

Sounds like business as usual to me, with a little sensationalization.

I would assume one major thing here is that many orgs only need a small subset of functionality from what most products provide. Many times, that small subset of functionality is only "good enough" in and of itself, but the org is paying the premium for the entire suite of whatever it is. This makes realizing that an LLM can get them to MVP and beyond much easier.

Charging hundreds of thousands if not millions per year for very basic functionality is what is "killing" b2b SaaS.

There is also the benefit of being able to use a single database (and hence schema) across multiple "apps". In many cases the complexity arises from the fact that all these apps have their own databases.

I'm not sure if this is the right place to ask, but does anyone else still work in an environment where they have to do synchronous version control? It's a nightmare and I have yet to find a decent solution.

To give an idea, this is a proprietary system that is extendable via scripts, but all of the artifacts are exported via XML files where script source is escaped into one XML tag within the metadata. Same with presentation layers, the actual view XML is escaped into one line within one attribute of the metadata file. The "view" xml may be thousands of lines but it is escaped into a single like of the export file so any change at all just shows that line as being changed in a diff. Attempts at extracting that data and unescaping it even seem to present problems because when the XML is exported often times the attributes within the schema are exported in a different order, etc.

I recently took a job maintaining and extending the functionality of an enterprise Enterprise Asset Management product through its own scripting and xml-soup ecosystem. Since it is such a closed system with a much smaller dataset of documentation and examples, it has been great at using what it does know to help me navigate and understand the product as a whole, and how to think of things in regard to how this product works behind the scenes in the code I cannot see.

It doesn't write the code for me, but I talk to it like it is a personal technical consultant on this product and it has been very helpful.