[-] vrek@programming.dev 1 points 3 days ago

Well basically it's just a 'magic number'. If you ban all of those many programs will either break or at minimum suffer sever performance degradation.

[-] vrek@programming.dev 1 points 4 days ago

Not saying it's nothing, most people just don't count it.

[-] vrek@programming.dev 1 points 4 days ago

Sweet! Don't tell my boss...

[-] vrek@programming.dev 2 points 4 days ago

Is that still true if I add vodka to the orange juice?

[-] vrek@programming.dev 2 points 4 days ago

I'm not the original poster but I think they meant the logo programming language. Basically you write a script which moves a turtle around on the screen and draws a line behind them.

It's unrelated to the Lego plastic bricks

[-] vrek@programming.dev 2 points 4 days ago

Ok yes sauces have calories but who really counts the sauce calories if you are already eating chicken nuggets? Like if you are eating a salad and count the dressing, maybe but the intersection of calorie counting people and chicken nugget eating people can't be very much

[-] vrek@programming.dev 3 points 4 days ago

Where is it not true?

[-] vrek@programming.dev 3 points 4 days ago

In my experience code review is often about the logic rather than the code itself. For example do you really need to copy the whole user object just to read their username? Can't you just pass the username in as a string instead? Static validation and test suites should already of eliminated any code errors. If you show up to a code review and the code doesn't compile, you're going to have a bad time. Stuff like calculating the same distance between two objects multiple times should be called out in code review, maybe extract that into a function. Reaching out to a database to get the same value repeatedly should be called out, maybe store it as a local variable.

One time I was reviewing some code which interfaces with an external third party piece of hardware which the api required the serial number for licensing. The programmer hard coded the serial number into the code. If we swapped it due to hardware malfunction we would need to update the software. If we got a second one we would need to maintain two code bases. This should be in a configuration file or something. Ai will not catch that. Static testing won't catch this. Test suites running on the piece of hardware we had, wouldn't catch this. Only a human reviewer would.

[-] vrek@programming.dev 5 points 5 days ago

My sister bought a house which came with a piano simply because the previous owners couldn't figure out how to remove the piano from the house...

[-] vrek@programming.dev 5 points 5 days ago

I have walked 500 miles and I will walk 500 more... Great now that song is stuck in my head

[-] vrek@programming.dev 9 points 6 days ago

It's fanuc cnc... Incredibly useful and precise but OLD! They literally still support programs from bubble tape if you need. It was basically hardware constrained initially but fixing it would break backwards compatibility which is a super selling point for them to government and long term industries.

Their controllers are mad expensive (budget version is like 30k last I checked), their support is top notch(tech typically on site within 24 hours with every possible board which may be bad so they can get you running and charge you later), they are incredibly precise and can do things other systems legally can not(a trainer I knew said "if you can move in 5 dimensions at once you can do some interesting things with nuclear energy so those require special clearance to sell"). Basically if you need them you NEED them, if you don't then you don't.

[-] vrek@programming.dev 10 points 6 days ago

It was g-code which as another commentator correctly pointed out was used to control a fanuc cnc system.

view more: ‹ prev next ›

vrek

0 post score
0 comment score
joined 3 years ago