IT/Software career thread: Invert binary trees for dollars.

ToeMissile

ToeMissile

Pronouns: zie/zhem/zer
<Gold Donor>
3,687
2,478
ShakyJake said:
Fellow employees at my org barely use it besides for simple questions. Technically we're limited to Microsoft Copilot but organization-scoped. I don't use it but I'm guessing this is a gimped model? Most complain that it's not great and lump all AI with that assessment.
Click to expand...
The default copilot w/M365 is solid for office/admin type stuff and even some basic coding. I’ve created a few little tools to help out adjacent teams. Usually just a standalone html file with embedded JS, one pulls out labels, notes and lat/lon out of .kmz/.kml files that the user reviews and manually uploads to our project management system. The other converts/bundles .heic images into PDF. Nothing fancy but it would take a couple weeks to get something like that request/built/integrated into an existing system, I did both in about a day including review with the people who would be using them
 
TJT

TJT

Mr. Poopybutthole
<Gold Donor>
46,546
127,171
Copilot is by far the worst of them. We have been using both Copilot and Cursor for a year or so. The entire engineering org favors Cursor by over 60%. Myself included.

I hear Claude Code is "better" but its terminal centric design is objectively worse than Cursor's IDE based design. At least if you're competing to get Java/Python/C/etc devs working with it. I am sure its quite dope for system engineers and what have you.
 
Last edited:
Khane

Khane

Got something right about marriage
21,549
15,448
I don't have much experience with the other agents but Copilot for sure needs to be guided, its still very useful but sometimes it outputs some truly absurd nonsense.

Last week I was troubleshooting an issue with invoking an external assembly that makes a database call from within xslt (don't ask). It really didn't know how to help with that, to the point that when I kept correcting it and letting it know its output didn't solve the issue it eventually started blaming the comments in the xslt, calling them malformed (they weren't). It was hilarious but also kind of tragic because there are probably vibe coders that very literally don't know something as simple as properly formatted comment tags in xslt/xml. And they would probably trust the agent to take them down that rabbit hole.
 
You must log in or register to reply here.