I am on a new team learning a new language and new frameworks, I can use all of the code review I can get. I need feed back, before I put a bunch of garbage into the code base. Code review is needed for new team members.

Webp’s purpose is to display images on web pages in a format that allows fast loading and rendering. When a user downloads or views an image it should be served in a better format. Webp serves it’s purpose perfectly. Don’t try to download a background of a webpage with the expectation that it will be in a format that is not beneficial to the pages function.

Why is it missing Haskell?

Fork is the best as far as GUI goes, but you can’t use a search engine to find any support information.

It’s an inference model. It does not understand code no matter how much context it has. It can however output the most probable solution based on the context it has.

I had CS exams that were coding only that i had to do on paper. For multiple classes. There is no debugging on paper.

“You know that temp shitty load balancer you wrote on your second month to get things up again. We still use it to this day.” My boss last week.

My team or I have not had very much luck with it. We were spending a lot of time picking out bad generated code.

It is not machine learning and LLM that pisses off Lemmy users. Its the application of said technologies. I don’t give a flying fuck what people are doing with ChatGPT, its novel. I want a generative AI that can help me code.

Especially HP printers and honorable mention to Konica Minoltas.

A lot of you have a lot of faith in people reviewing PRs. I know a few Sr. developers, that if shit was too busy, would skim it and say 'fuck it, it will be QAs problem. If you put this in the correct sub-system in file that would only be executed once a month, for example a maintenance class, It would be really hard to notice something is wrong if it didn’t cause issues seen immediately. Maybe this is the story of an intern that added something that also fucked up boolean comparisons in a subsystem used once a month. Where there is a 2 week lag between the execution and operations noticing something wrong.

I learned this the hard way, I forgot to commit for a single day and got burned really bad when my regression tests failed and I could not trace the issue(it is called source control for a reason). I declared it was more efficient to revert back to the last commit than spend time fixing broken code that I had no fucking clue where it was and the only thing I had to go by was that it happened between two commits with a whole work day between.

One day you will inherit a code base so bad that you’ll end up commenting old code just to make sense of it for yourself because nobody in the company has touched in a couple years and the last people that did no longer work there. It will be dangerously coupled, if you make the right change somewhere it will break everything else. It will be true spaghetti code where you spend 30 min just following a code path to figure out what and why an input into a function needs to be what it is to able to come out of another function in an exact format for anything to work.

Your so called comment standards and principals are fine if you are building something from the ground up, but the other 95% of the time, you do what you gotta do because your were blessed with a turd that is impossible to polish.

Canadian Engineering Associations will actually get you for illegally labeling yourself an Engineer. I did a software developer program and after graduating a few people decided to start calling themselves engineers. The organization contacted each person individually and I belive the program coordinator. It is a serious title here, it is the same as a healthcare worker calling themselves an RN without being registered with the nursing college.