Hacker News new | past | comments | ask | show | jobs | submit | nathan_douglas's comments login

That’s really cool.

Something I struggle with, regarding social and semi-social functions at work, is just having the willingness at the time of $event to actually join it — a “social hour,” an engineering CoP, whatever.

I feel like this sort of thing would be good and healthy, but I honestly kind of feel like I’d end up dreading it nevertheless.

I feel sometimes like my ability to even _want_ to make friends is broken, heh. Is that semi-relatable?


This is pretty common and being primarily made up of parents family stuff often comes up last minute but from what I've seen the people that make it to one and break through that mental barrier seem to be more and more excited each month.

While it is a social group if you're not feeling super social one month you can join in remotely or just show up head down and get some group gaming in. There is no pressure.


It's 100% relatable.


That's a really neat idea! I think I'll try to work that into my own Lox derivative :)


Let me know how it goes!


They pop up in code repositories too, depending on contents and whether the engineer in question noticed it.


absolutely essential to add a line for .DS_Store in every .gitignore, unfortunately.


Enough to teach people to use a global git core.excludesfile, IMO.

Same place you should put rules for Emacs / Vim swap files.


Totally correct. Files which are unrelated to the project don't belong in .gitignore.


This may be technically correct, and I do have .DS_Store in my global, but I also put it in projects, because I know not everyone on my team is going to do that. I add it to the .gitignore in projects to save me from other people junking up the project. It’s a lot easier to add some lines to a file than it is to micromanage the global file for every potential future contributor.


This touches on something I've learned to be more mindful of: the "right answer" (especially to a techie) is often not the right answer in real world cases.


I’m fine with the occasional .DS_Store getting added, because you can just remove it afterwards. Most of my work is either my own projects or at work, and whether people at work commit .DS_Store files is a question that touches on code reviews, company onboarding guides, etc.

Maybe the benefits / drawbacks would be different for an open-source project with a lot of contributors.


Just add a like to your onboarding docs to teach what the global ignore file is and how to manage it. the have them add a line for DS_Store.


It makes sense to add an ignore for .* though and then specifically unignore only those dotfiles/directories that you actully want checked in.


or just ignore them globally once.


I've banned people before because they couldn't stop themselves from continuously uploading those useless ds files


Seems like you have control issues.


Nah, those people have issues controlling their machines. It's fine if you upload useless spam a few times, but at some point you need to quit it because you're creating unnecessary work for others.


Well I was trying to tell you nicely, but you’ll figure it out before long.

Banning someone because they commit a file you don’t like is definitely a sign of a controlling person.


Repeatedly. Besides, if you repeatedly pay such little care how can anything you do be trusted?


You’re right, people are born perfect so this is felony behavior. We should limit their rights as a result.

Thanks for giving me a new interview question.


Stop being ridiculous. If you can't learn from your mistakes, even after it has been explained to you several times, you're the problem.

> limit their rights

Now you're just being weird. No one has an inherent "right" to contribute to a project.


Yea you missed the point. The point being you’re overreacting to a nonissue. But regardless it’s easy enough to filter your types out of my own projects and teams so I don’t care anymore.


lol, ok bro. glad to not have to work with you as well since you're really channeling that "can't learn from my mistakes and will keep burdering others with them! Wait, why don't you like me?" energy


so we beat on, commits against the tooling, borne back ceaselessly into the technical debt


What does “going cold turkey on food” look like here? Because I’ve quit a pack-a-day-for-ten-years nicotine addiction, and I’ve dieted by slightly increasing exercise and slightly decreasing caloric consumption to produce a daily deficit of about 250-500 calories in line with mainstream medical recommendations, and I can tell you which I found harder… and it wasn’t drinking diet soda and walking around the block in the morning.


I suppose the cold turkey equivalent here is intermittent fasting. Disciplining yourself to ignore the most basic instincts of survival and eat at a specific time.

I never smoked nor fasted, so I can't really compare the two.


I’ve always liked “I’ll burn that bridge when I get to it.”


I just heard a podcast that mentions "we’ll burn that bridge when we come to it". There's a transcript here: https://www.quickanddirtytips.com/qdtarchive/mixed-metaphors...

Here's the relevant part: "sometimes people also like to play with mixed metaphors. It can be a fun way to turn a cliché on its head. For example, I’ve seen people mix the metaphors “Let’s cross that bridge when we come to it,” meaning let’s put off the decision, and “Don’t burn your bridges” meaning don’t destroy a something you’ll need later. They get “We’ll burn that bridge when we come to it,” which combines the meaning of the two metaphors into something like “We’re ready to fight when the right time comes,” and still maintains imagery that makes sense."

"We’ll burn that bridge when we come to it" seems to be considered a mixed metaphor, rather than anything more exotic.


I have not heard that before. My somewhat litteral spectrum disorder brain implies the bridge is burnt before it is crossed.

Common ones I hear are "I'll cross that bridge when I come to it" - to delay an action or decision and "Don't burn (all) your bridges..." - leave a path open for a reversal.


> the bridge is burnt before it is crossed.

That’s the usual interpretation I’ve seen, yes. It’s a mix between the other two metaphors you mention, with the humorous implication that the speaker is going to delay taking an action until dealing with it will cause further problems.

Example sentence: “My manager doesn’t know I can’t work on Wednesday, but he hasn’t posted the schedule for the week yet so I’ll burn that bridge when I get to it.”


Ah, yes. I see that now. Thank you.


Brooks & Dunn had a semi-popular song in the 90’s that used a variation on that: https://youtube.com/watch?v=ZxIwlV9qOZs


One bridge at a time


If you have something like 1Password, it takes one or two clicks to set up 2FA for a given site and Passkey setup for a given site is pretty painless. There’s even a decent amount of CLI integration for signing commits, etc. As a federal contractor working in and out of higher security areas, 2FA and Passkey are… really not intrusive or disruptive to my daily life.


On the other hand, though, it reminds me of the song “Particle Man.”


According to the CDC, it seems about 6 people die per day of alcohol poisoning, or ~2,191 per year, so about .07%. Nearly 3/4 are men, which doesn't particularly surprise me, but what does surprise me is that the average age was 49 years, and only 5% were aged 18-24. I would've expected the numbers to be shifted left far more than that. Also interesting was that the overwhelming majority (71%) had a long history of alcohol use problems. In 58%, death was attributed solely to acute alcohol toxicity, but in 42% there was an underlying disease present as well. Huh.


~3 million is number of first time drinkers not the total number of people drinking alcohol in the US. ~180 million people drink alcohol one or more times a year so 2,191 per year is ~0.0012% per year.

The risk on the first time they consumed alcohol is probably 1/100th of that due to younger ages etc.


Do you mind sharing what your industry is? Just out of curiosity.

I’ve been programming side projects in Rust for a few years now, but wouldn’t really feel comfortable doing it for a living. Reading through occasional RFCs, without.boats, etc makes me feel like an absolute idiot.


consumer robotics


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: