Programming

17696 readers

208 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 2 years ago

MODERATORS

snowe

Ategon

[email protected]

thrown into a backend project as a backend dev with a language I don't know, how fucked am I? (lemmy.world)

submitted 1 year ago by [email protected] to c/programming

53 comments fedilink hide all child comments

The title itself is a recipe for disaster. Also this is a semi rant.

Yesterday I was informed that I will have the honour to implement the core functionality - which is an interface layer to use the driver of a very expensive hardware shit - of the software I’ve been working on as a frontend dev.

There are two possibilities for the language: C++ or C#. The one that was proposed/imposed is C#, which I know nothing of, while at least I have some hobbyist experience with C++; when asked if I could take some time to familiarise myself with C# I was basically laughed in the face, saying I will learn on the field and at least some of them have some experience with it.

Should I insist to go with C++, or is that an even worse idea in an already fucked up situation?

you are viewing a single comment's thread
view the rest of the comments

[+] [email protected] -13 points 1 year ago (1 children)

You have copilot? You'll be fine if so, just throw down comments for what you want it to do and tweak it when it doesn't compile.

[–] [email protected] 15 points 1 year ago (2 children)

Please do not follow this advice. For one, copilot is terrible in general. For two, using it without being able to vet the codes correctness is a recipe for disaster.

[–] [email protected] 3 points 1 year ago

copilot is terrible in general.

I concur. I took the free trial and was not impressed - most of the time the suggestions aren't any better than LSP autocomplete.

And if I asked it to implement something or let it autocomplete part of (say) an expression, it tends to go tits-up completely. (Which is especially odd considering I use languages with abundant static context - It's not like JS where the type of a function parameter is "who the fuck knows until runtime.")

Spend your $10 a month on supporting OSS devs/projects.

[–] [email protected] 2 points 1 year ago (1 children)

I think that was the joke?

[–] [email protected] 1 points 1 year ago

We hope