I object to the notion that having "american born engineers" is the cause of their issues.

It ain't the cause, but is definitely an enabler, because foreign talent on work visas effectively depends on their job much more so than their domestic counterparts and are thus very unlikely to push back against unreasonable demands or workload.

I don’t watch sitcoms anymore. I come read HN for these gems.

No but it demonstrates a disinterest in building software products and a bigger interest in playing business cost economics and securing their moat. Part of their strategy to force as much money into AI-hype as possible.

We may as well call them working hostages.

Yeah, that was unnecessary. Incompetent are born and work everywhere. In this case, Microsoft's problem with GitHub is trying to shove the square peg that is GitHub in to the round hole that is Azure.

Welding is coming along. Ever heard of Path Robotics? That's high-mix, high-complexity welds. (There are a lot of other, less-sophisticated welding robots out there.) The biggest moat for a welder right now is special certifications to be able to do welds on submarines, etc.

I tried to build this back around 2020. I think my concept was trying to be too cute in several places. But this was the basic idea.

I found that neither side of the market wanted to rethink the market, they just wanted something that worked well for them. Even today, job seekers may be reaching for something like this but employers have no interest; there is a glut in the market.

I’m sure I never quite got the messaging correct. However, I distinctly recall that triplebyte attempted a pivot in this same vein and also failed bad.

They are shutting down the product. I haven't received the sunsetting guide. What are people moving to instead?

Check out https://minfx.ai

i moved from wb to neptune because of wb's slow ui, i loved neptune so much i'm seriously considering building a "clone" https://arago.dev . If anyone's interested in using or helping building it, hit me up.

Weights & Biases if they are serious and need performance and scale.

We are very serious about performance and scale, and have extensive experience with it. Check out https://minfx.ai

WandB and performance/scale, name a less iconic duo. There’s a reason many labs switched to Neptune.

These prompts read a lot like wizards’ spells!

I was gonna say. "to bind your spell true every time, let the spell be spake in rhyme" doesn't just work on spirits, apparently.

Can you provide some examples?

If medicare increases payouts then the payoff to this sort of behavior only increases.

Fair enough. However, I still think with better aligned incentives you could drive down undesirable behavior.

I've been mostly pleased with our use of python-polylith [1] with poetry in a production application. We output a webapp, python sdk, and CLI as separate "projects."

It doesn't _really_ solve python dependency/import issues. Instead, it helps to you keep your project in discrete chunks and well-organized. It also makes it easy to package up the separate projects as artifacts.

I've run into some issues with versioning separate projects but I suspect that is a matter of bandwidth rather than an actual, insoluble issue.

I'd use it again at a startup or on project where you need to ship a bunch of artifacts but don't have a lot of bandwidth.

[1] https://github.com/DavidVujic/python-polylith

Are there any comparisons of weather apps by area? For example, "for the San Francisco bay area, apple weather is most accurate on rain. But for NYC accuweather is better." I suppose you ought to be comparing weather APIs rather than apps but it would be most usable if you just knew which app to download.

Not really apps, but here's a tool that can do it by forecast data source: https://www.forecastadvisor.com

I would be careful with LaTeX. I use to have a LaTeX resume generated with LuaTeX. At an old company, I saw my LaTeX resume in the ATS long after I was hired. Apparently, something happened and the PDF displayed as blurred-but-not-unreadable in the ATS. Maybe the ATS did some post-processing or used a limited PDF display engine? Lucky for me, the resume for that job was just a formality. These days, I just use Google Docs and export to PDF.

I've made sure all the most commonly used ATS systems can read the produced PDF without issue.

I wouldn't worry about automated ATS. Their use is way overstated on LinkedIn, by "resume experts," etc.

I'm talking about whether a human can read the document comfortably.

Do you have any tips, code, or even just a list of the common ATS systems? I need to do this with my latex cv but I'm not even sure where to start.

I think this open-source parser details a typical ATS algorithm: https://www.open-resume.com/resume-parser

I don’t know of the example systems but I’ve applied to a handful of companies recently, all running the same-ish workday resume ingestion. You can actually tell which are running a more recent version because the parsing is more accurate.

There is also a common no-account single page application software, I checked at a company I’d applied to and it was called Lever(?)

Normally, I thought for ATS parsing if you upload in an application and a few of the prior experience text boxes are accurate, then you’re good. I’ve always had to fix my experiences though, even with using a word doc.