consistent language
Forsooth, I find thy point fit only for the jakes.
consistent language
Forsooth, I find thy point fit only for the jakes.
Hate to break it to ya boss but part of speech is descriptive, not prescriptive. Childish would be insisting that every word stay in the tidy little box assigned to it rather than recognizing and appreciating language’s flexibility and constant evolution.
They’re definitely better entertainment pound-for-pound. I’d contend that the book gives you a lot more to think about, so it really depends what you’re after. I like them both a lot–I think they complement each other very nicely.
does adding the copyright/license information do anything?
Not a lawyer, but I’d be sore amazed if “your honor, he copy/pasted my Lemmy comment” flies in court, regardless of your copyright status. The same goes for those AI use notices–they’re a nice feel-good statement, but the scrapers won’t care, and good luck (a) proving they scraped your comment, (b) proving they made money on it, and © getting a single red dime for your troubles.
Gentrification and weed. When I was growing up, there were large swathes of town where you just didn’t go after dark. Now they’re all brand new office and lab space punctuated with dispensaries every couple of blocks.
Eh, depends on the language and the context. I still use 80 for C, but I’ve found 120 to be a much more reasonable number for Java.
Board state in marketing photos cracks me up. Who needs corners? What is a big move? Attachment fights only pls
I’ve been migrating one of my company’s apps from microservices back to monolithic Java. It’s wonderful. I haven’t touched a line of yaml in weeks.
I read that one, he literally described himself as mediocre programmer and is excited about gpt as a way for mediocre programmers to be competitive again. I’m sure he’s in for a really fun time when he has to find a bug in 12k lines of AI spaghetti he bolted together.
doesn’t understand that this is a useful first step in debugging
reacts with anger when devs don’t magically have an instant fix to a vague bug
Yep, that’s a manager
Haven’t seen this one on Mlem
~In a modern title designed to be played at 60+, definitely. I’ve been having a blast in dark souls 1 and GTA:SA recently, both of which are capped at 30. Older games are made to work at that FPS, and it takes remarkably little time to adjust and have it feel normal. If I tried to play armored core at 30fps, on the other hand, I think I’d rip my teeth out in frustration.~
Edit: misinterpreted the comment above as “unless it’s VR (i.e., in all cases except VR), you are not having fun” rather than “unless it’s VR, in which case you are not having fun.”
In my experience refactoring lots and lots of crappy code left by devs long gone, a dev who can write useful comments is by and large a dev who can write code clean and simple enough not to need them. If the code doesn’t have informative names and clear separation of concern, chances are a comment won’t help because the dev didn’t really know what they did that worked in the first place.
I presumed it to be a standin for just directly using Math.max, since there’s no nice way to show that in a valid code snippet
Not using thief is professional incompetence unless you’re doing something deeply cursed
Isn’t that how the matrix 3 ends?
I was super drunk when I watched it but I feel like that’s the compromise they reached
I’ve been tasked with updating some code a senior programmer (15+ years experience, internally awarded, widely considered fantastic) who recently left the company wrote.
It’s supposed to be a REST service. None of the API endpoints obey restful principles, the controller layer houses all of the business logic, and repositories are all labeled as services–and that’s before we even get into the code itself. Genuinely astounding what passes for senior-level programming expertise.
That’s what’s really irks me be about JS–you can do just about whatever but you’re not supposed to.
It’s an imperative language, but best practices are to use it functionally.
You can omit semicolons, but best practices are to use them.
You can use sloppy equality, but best practices are to always use strict.
In my experience, very, but it’s also not magic. Being able to package an application with its environment and ship it to any machine that can run Docker is great but it doesn’t solve the fact that modern deployment architecture can become extremely complicated, and Docker adds another component that needs configuration and debugging to an already complicated stack.