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.

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 think it is fair to say that having skin in the game suggests that they are making these ethical judgments in good faith; that is, that they genuinely believe that they are making the ethically correct choice in propagating their brutal war. I do not, however, think that level of personal liability inclines them any more strongly towards making genuinely ethical decisions, only ones that they genuinely believe to be ethical.

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.

“Never use a knife as anything but a knife or you’ll end up disappointed and with a broken knife.”

Not sure where I heard that first, but it’s stuck with me.

I have a friend who was a classic Catholic libertarian in college–he held some views on trans rights, abortion, and economic justice that I find deeply disagreeable. It made conversations a little tricky because there were a whole set of topics I couldn’t bring up unless I wanted to wade into a debate immediately; sometimes I did, but often I just wanted to hang out and chill and that was hampered.

It took him exactly one year of being out of college and working a real job to realize that his economic views were fucked, and the whole rest of it unraveled from there. He’s now a staunch leftist, and it’s way, way easier to hang out with him.

That’s not, however, to say it’s not worth having friends you disagree with. We remained friends because we were able to disagree productively, and I feel I understand my own political views far better for all those long nights discussing them. Still, it was a friendship that took unusual effort to maintain.

My big dumb orange boy loves to sit right in front of the subwoofer. I guess he’s a metalhead at heart.

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

I’ve been perusing their website for a little while now, and there is a rough pattern:

At least for acoustics:

• The first two letters are the series. This is the most variable component, but follows some loose guidelines:
  • The initial letter is often indicative of what what onboard electronics that series of guitar comes with, even if the particular guitar doesn’t have them (C guitars come with Fishman CD-1, F come with Fender, P come with Fender/Fishman sonitone plus). This letter is sometimes omitted (see the simple D10 dreadnought)
  • The second (or first, if there is only one) letter generally indicates the body style. D is dreadnought, C is concert, B is bass (or banjo!), O is orchestra (?)
• The number generally indicates quality. Bigger number more expensive within a series.
• S after the number indicates a solid top (no S indicates laminate)
• C after the number indicates a single cutaway body
• E at the end indicates that the guitar has onboard electronics

Personally I found the combat as fun and balanced as can be expected in a game where power scaling is not directly tied to progress. If you just fuck around doing side quests and farming loot for 20 hours, it’s going to feel super easy, and if you try to blitz the story and run early game stuff then enemies will feel like bullet sponges. That’s just a mechanic endemic to the open world rpg genre. My first playthrough I did side missions as I stumbled across them on my way through the story, and the combat felt pretty balanced. Second time I went much more methodically and ended up cruising through story missions like nobody’s business.

Are you FOSS?

Mlem. There isn’t really a main reason. I like it because:

• It’s native SwiftUI, so it feels super snappy and “Apple-y” the same way Apollo used to
• It’s FOSS (though that’s sort of table stakes around here)
• The widget customizer thingy on the beta build is absolutely fantastic
• It’s not ugly. There are a bunch of apps that just sorta aped the Apollo UI without any of the attention to detail
• I have a ton of faith in the stability of the dev team. There was a bunch of drama early in its development and I was pretty sure the project was going to die, but it didn’t and it’s been (as far as I can tell) smooth ever since

My only gripes are that the scrolling is still sometimes funky on the beta build and development isn’t the fastest, but once all the apps are in their fully-built stable state I think Mlem is absolutely going to stand out among the crowd.

There are a lot of good resources in this thread, but nobody has mentioned the single most important part by far:

actually practice philosophy

Study is worthless if you don’t engage in the practice of philosophy. Find people to debate with, preferably ones who have a formal grounding (and I mean a real debate, where you make reasoned arguments and investigate the truth of a matter, not the bullshit-flinging points game that gets popular online). Write arguments, revise them, give them to people to tear them apart.

The literature is good, but it will only teach you (a) how philosophers approach questions, (b) what arguments and counterarguments have been successful or popular, and © what the big questions are. If you do not practice philosophy, you will never learn philosophy; you will only learn what philosophers have said.

Yet another thing the lord of the rings movies absolutely nail. The evolution of the Rohirrim theme from a single lonely violin when Gandalf and co. arrive in Edoras to a grand orchestral arrangement over the assembled host gets me every time.

Passed mine first try. It helps to take it somewhere suburban-almost-rural–the roads will be way easier and the instructors are more inclined to pass people because it’s much more important for people in those places to have licenses.

Mlem. I miss Apollo dearly, and used Voyager for a bit, but while it’s faithfully aped the UI you can feel that it’s mobile in a way I just can’t stand–it’s sludgy and just subtly off. Mlem is snappy and feels at home on an iPhone in the same way Apollo did, even if it’s still a little rough around the edges.

I’ve slept on futons (thick, dedicated bed futons, not the couch/bed combo) basically all my life, I personally think they’re fantastic. Reading these comments it seems like the sort of thing that either really works for you or really doesn’t–I am fairly tall and have a back that loves to complain, but it gets along swimmingly with my futon.

Cheap, thin futons are a nightmare though. Even nice futons tend to be cheaper than most traditional mattresses, so it’s never worth cheaping out if you don’t need to.

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.