your company has money for no one above mid-level engineers to be actually building the product?
Solitary, poor, nasty, brutish and short
your company has money for no one above mid-level engineers to be actually building the product?
tldr - you’ll just have to do the conversions in your head now because it’s useful to know where the sun is at different points on the earth when trying to communicate across those points.
the fact that the acronym for Coordinated Lunar Time is LTC tells you everything you need to know about how this will work.
throw new SameJokeException();
because you use the root account on linux occasionally to do one thing but when you’ve got a rooted phone everything is done with the root account
windows update kept downloading these bloated “updates” that included brand new software that I didn’t want or use, broke my settings, added a bunch of spyware, adware and other shit and slowed down my system
installing linux fixed that instantly and permanently
this, but doubly so with Eve. You’ll notice that we often skip over Cindy and Dave and go right to Eve, so often that I don’t even know off the top of my head whether Charlie and Deandra are the conventional names for persons 3 and 4 in this construct. That’s because this construct is used a lot when talking about secure communications and the convention is that “evil” “eavesdropping” Eve is the person trying to destroy, intercept or alter the communication between Alice and Bob. Her role is built into her name.
only through private ownership of property and capitalist competition can good ideas emerge and be adopted
his “putting on a show of being angry for the cameras” is a bit below average tbh. people who’ve never been in a kitchen find it shocking, and the rest of us are like “well he didn’t actually break anything and the idiot sandwich thing was really funny”
18 years in restaurants checking in: Gordon Ramsay is not very far from the mean at all. In fact, I’d say he’s a mean mean man of average rage, and it’s the nature of the industry that does this to us. It’s flat-out abusive even in its best implementation, and the far and away vast majority of restaurants are purposefully exploitative. This goes double for back of house. I was usually a server or bartender, though I did work every hourly position at some point in my career. Front of house at least gets compensated more the busier they are. Back of house gets what they get whether they sell two orders of fries in an evening or they spend all shift with ten tickets on the rail and 30 open menus. Back of house also doesn’t get paid all that well, outside of a few rockstars. It’s a super high stress position, and that stress level is completely unpredictable. Any random Tuesday afternoon you could find yourself behind the line all alone as the third bus pulls into the parking lot. The extremely variable nature of the stress means two things:
You don’t cook as a career unless you love turning out great food. You might do a couple years just because you need a job but it’s so hard on your mind and body that after a while you literally either love it or leave it.
Eventually everyone in the kitchen becomes what Robert Anton Wilson called “…the walking wounded…slightly deranged by either anxiety or grief.” There’s a lot of PTSD in kitchens and, because hurt people hurt people, it tends to spread to new people and reinforce itself in veterans. In the highest volume store I ever worked in we used to joke that sexual harassment and bullying were just how we said “Hello”. It’s not okay, but it’s the reality on the ground. It tends to develop spontaneously because of the way restaurants work and once it takes root it’s really hard to get rid of.
So the average restaurant worker is half Anthony Bourdain, here for the love of food and people, trying to experience new and great things and build new and great things for other people to experience just out of a general enthusiasm for humanity. He’s also half Gordon Ramsay, throwing an overcooked steak back at you because a cow had to die to make it and our guest had to sell a little bit of their life to afford it, so you will fucking respect both of their sacrifices and turn out some good fucking food. It’s love, and it’s pride, and it’s trauma, and it’s passion for what is essentially an unrecognized folk art. And if it paid the bills I’d go back in a heartbeat.
it’s only dumb til it works
what if we just finger and mount?
I didn’t miss the sin. The sin isn’t relevant to me. You don’t treat people like that. Whatever you hope to accomplish, you can accomplish without treating people like that. If someone else is being abusive, that’s not license for you to be abusive in response. If a cop was abusing their power would you expect the chief of police to publicly berate and insult him, or would you expect the standards to be enforced without resorting to that?
When you abuse someone for being abusive you don’t make it clear that abuse is unacceptable. In fact, you do the opposite. You establish that abuse is a part of your culture. If I was considering contributing to the kernel and saw this exchange, I’d walk away. I don’t need that shit, not from Mauro, not from Linus, not from the Lord hisownself. It damages the organization long-term.
you seem to have created a false dichotomy where it’s impossible to fix bad code without being abusive. would you like me to call you “dumb motherfucker” or is this explanation enough?
looks like every day is a great day to not work on the linux kernel
`//Get CustomerInfo from CustomerRepository by Customer ID or else throw an CustomerNotFoundException
public CustomerInfo getById(String customerId) {
return customerRepository.getById(customerId).orElseThrow(new CustomerNotFoundException());
}`
This is the kind of pointless comment I see in my codebase all the time. Best I can tell, a couple of my coworkers like to plan out their code using comments, then backfill in the actual executable code. That’s fine, but they leave the comments in when they add no value.
` public static LocalDate parseEndDateFromString(String dateString) {
try {
String[] split = dateString.split("-");
//In order to get the last day of the desired month, we go to the first day of the next month, account for rollover, then subtract one day
int month = Integer.parseInt(split[0]) == 12 ? 1 : Integer.parseInt(split[0]) + 1;
return LocalDate.of(Integer.parseInt(split[1]), month, 1).minusDays(1);
} catch (Exception e) {
throw new RuntimeException("Invalid date format - must be MM-YYYY");
}
}`
Stuff like this, otoh, is where comments are useful. The required format is obvious from the error message, the param and return from the method signature, the only part that requires a comment is the fiddly logic of accounting for the edge case where month == 12 and the rationale behind how we determine the last day of the month. As a rule, comments are for why something is being done, if it’s not obvious, and for magic numbers. Code should tell you what code does.
edit: can anyone spot the bug that I introduced with that parseEndDateFromString() method?
the question here is, on it’s face does an invasion of privacy constitute an injury? I’d argue that yes, it does. Privacy has inherent value, and that value is lost the moment that private data is exposed. That’s the injury that needs to be redressed, regardless of whether or how the exposed data is used after the exposure. There could be additional injury in how the data is used, and that would have to be adjudicated and compensated separately, but losing the assurance that my data can never be used against me because it is only know to me is absolutely an injury in and of itself.
I have a feeling they’re not just FreeBSD enthusiasts being pedantic…
not my experience at all across 3 separate companies. Ime senior engineers are the highest level that still spends most of the day heads down most days, and that’s why I’m gonna stick it out at this level as long as I can.