I have a feeling F# would work great, but unfortunately we don't use it at work so I can't experiment with the fancy expensive models. Only problem might be amount of training data.
It's easier to be lazy now more than ever. Hard to blame them because the temptation to deliver and prove oneself as a junior is always high.
I can't count how many seniors have forgotten what it means to understand the code they're merging since AI coding tools became popular. So long as businesses only value quantity the odds are stacked against juniors.
Don't bother. They're going to claim that cosmic radiation can alter bits so compiler determinism is comparable to LLM. I'd rather AI evangelists claim determinism is not required to build decent software than perform the mental gymnastics required to make these comments.
By those metrics, Microsoft lost 20% of it's value due to hopping on the AI coding assistance train.
I'm not saying it is the case, just making it apparent how unreliable it is to measure productivity by comparing what's happening at the lowest level in a company to its financials.
Oh, so Microsoft can never, ever, possibly resurrect the product or even name of the product again? This is even more reason why it was probably a better place tp put features like a markdown editor.
They are trained on our code. Perhaps not if you don't have any of it open sourced, but it's so jarring to see someone say they don't care about our code.
My experience in the Teams org is the same. It's all about security, compliance, and recently AI. Fixing bugs and similar "non-flashy" work is a sure way of postponing one's promotion indefinitely.
reply