Dan Stoner @thatlinuxbox

I had a lot of fun making this video on my Turkey Trot 10k race. youtube.com/watch?v=Yced3x…

The people who say they want to see a revival of US manufacturing often don't actually support it. They're the ones who will buy the cheaper t-shirt every time, which means the one made abroad. Meanwhile, the luxury consumer doesn't care where something is made but will pay $$$.

My doctor, a board certified neurologist with over 20 years of experience believes I need an MRI. But Frank, from Blue Cross Blue Shield, believes otherwise. What a joke.

This dog's name was Gunner. My uncle brought him back from WW2. He was raised and slept under my uncle's anti- aircraft gun. The gun crew shared their rations to feed him. By the time he was 18 months old, my uncle said he would stand up and look at the sky. If he laid back down they knew all was ok. If he growled and put his hackles up they got at the ready. He knew the sound of the German aircraft and my uncle said he never got it wrong. He said Gunner was better than any early warning system. I'm probably the only one left in the family that knows that story now, so I thought I'd tell it before it's lost forever, like many stories must be from that time. Thanks for reading it. Credit - Smoky War Dog LLC

HOLY LORD, every Christian must see this!

he wrote this in 2009 and some still do leetcode problems on interviews

The strength this takes x.com/visualfeastwan…

2) 🥇 Award for the best "self-improvement insight" goes to @jeanqasaur

The 37signals Guide to Internal Communication The how, where, why, and when we communicate. Long form asynchronous? Real-time chat? In-person? Video? Verbal? Written? Via email? In Basecamp? How do we keep everyone in the loop without everyone getting tangled in everyone else’s business? It’s all in here. Rules of thumb, and general philosophy Below you’ll find a collection of general principles we try to keep in mind at 37signals when communicating with teammates, within departments, across the company, and with the public. They aren’t requirements, but they serve to create boundaries and shared practices to draw upon when we do the one thing that affects everything else we do: communicate. 1. You can not not communicate. Not discussing the elephant in the room is communicating. Few things are as important to study, practice, and perfect as clear communication. 2. Real-time sometimes, asynchronous most of the time. 3. Internal communication based on long-form writing, rather than a verbal tradition of meetings, speaking, and chatting, leads to a welcomed reduction in meetings, video conferences, calls, or other real-time opportunities to interrupt and be interrupted. 4. Give meaningful discussions a meaningful amount of time to develop and unfold. Rushing to judgement, or demanding immediate responses, only serves to increase the odds of poor decision making. 5. Meetings are the last resort, not the first option. 6. Writing solidifies, chat dissolves. Substantial decisions start and end with an exchange of complete thoughts, not one-line-at-a-time jousts. If it’s important, critical, or fundamental, write it up, don’t chat it down. 7. Speaking only helps who’s in the room, writing helps everyone. This includes people who couldn’t make it, or future employees who join years from now. 8. If your words can be perceived in different ways, they’ll be understood in the way which does the most harm. 9. Never expect or require someone to get back to you immediately unless it’s a true emergency. The expectation of immediate response is toxic. 10. If you have to repeat yourself, you weren’t clear enough the first time. However, if you’re talking about something brand new, you may have to repeat yourself for years before you’re heard. Pick your repeats wisely. 11. Poor communication creates more work. 12. Companies don’t have communication problems, they have miscommunication problems. The smaller the company, group, or team, the fewer opportunities for miscommunication. 13. Five people in a room for an hour isn’t a one hour meeting, it’s a five hour meeting. Be mindful of the tradeoffs. 14. Be proactive about “wait, what?” questions by providing factual context and spatial context. Factual are the things people also need to know. Spatial is where the communication happens (for example, if it’s about a specific to-do, discuss it right under the to-do, not somewhere else). 15. Communication shouldn’t require schedule synchronization. Calendars have nothing to do with communication. Writing, rather than speaking or meeting, is independent of schedule and far more direct. 16. “Now” is often the wrong time to say what just popped into your head. It’s better to let it filter it through the sieve of time. What’s left is the part worth saying. 17. Ask yourself if others will feel compelled to rush their response if you rush your approach. 18. The end of the day has a way of convincing you what you’ve done is good, but the next morning has a way of telling you the truth. If you aren’t sure, sleep on it before saying it. 19. If you want an answer, you have to ask a question. People typically have a lot to say, but they’ll volunteer little. Automatic questions on a regular schedule help people practice sharing, writing, and communicating. 20. Occasionally pick random words, sentences, or paragraphs and hit delete. Did it matter? 21. Urgency is overrated, ASAP is poison. 22. If something’s going to be difficult to hear or share, invite questions at the end. Ending without the invitation will lead to public silence but private conjecture. This is where rumors breed. 23. Where you put something, and what you call it, matters. When titling something, lead with the most important information. Keep in mind that many technical systems truncate long text or titles. 24. Write at the right time. Sharing something at 5pm may keep someone at work longer. You may have some spare time on a Sunday afternoon to write something, but putting it out there on Sunday may pull people back into work on the weekends. Early Monday morning communication may be buried by other things. There may not be a perfect time, but there’s certainly a wrong time. Keep that in mind when you hit send. 25. Great news delivered on the heels of bad news makes both bits worse. The bad news feels like it’s being buried, the good news feels like it’s being injected to change the mood. Be honest with each by giving them adequate space. 26. Time is on your side, rushing makes conversations worse. 27. Communication is lossy, especially verbal communication. Every hearsay hop adds static and chips at fidelity. Whenever possible, communicate directly with those you’re addressing rather than passing the message through intermediaries. 28. Ask if things are clear. Ask what you left out. Ask if there was anything someone was expecting that you didn’t cover. Address the gaps before they widen with time. 29. Consider where you put things. The right communication in the wrong place might as well not exist at all. When someone relies on search to find something it’s often because it wasn’t where they expected something to be. 30. Communication often interrupts, so good communication is often about saying the right thing at the right time in the right way with the fewest side effects.

@TechSquidTV In theory a good company will be great in all departments. In practice for many companies the engineering departments are great but their HR requires improvement.

Migrations are second only to outages for training and learning purposes, and for developing a sense of ownership over your systems. Don't waste them! Also terrific for building xfn relationships and camaraderie. Doing big things together builds bonds. 🥰

How I learned to love writing tech documentation and how you can get other people to love it too (including yourself). A thread.

Orville Rogers is 100 years old. He set a new age record by running the men's 60M in 19.13 seconds.

Dogs can love cartoons too. 😂

when i was a young engineer, I once asked an older engineer why he didn't keep any books around for the programming language we worked in. he told me that in his experience the books someone owns are more about what they wish they knew rather than what they actually know

How I spent 1996: My boss wandered into my office and said "Hey Dave, do you want to rewrite pinball for Windows NT?". I said "Hell ya" and got paid to write and play pinball for two months... while listening to Soundgarden. And kudos to the original designers for a classic!

@InternetH0F Wait for it🥸

👏👏👏