mastersummoner

Not that I'm particularly familiar with the average Eritrean's diet, but going out on a limb here: are you implying that starvation is better for a person's well being than an overly calorie-rich, generally unhealthy but plentiful diet?

Seems good. My biggest problem with Teams isn't performance though, which has generally been fine for me on the Mac M1 chip, but how awful a lot of their text formatting is.

Try creating a code block (``` followed by a space), or inline code (`my code`), or even a quote block (> heya) and you'll see how inferior the UX is to Slack. Losing the ability to exit the created block is the biggest flaw, but it's also extremely tricky to just get things to look how you expect them.

Also, this is kind of dumber but I really wish there were more emoji reaponses. Slack got me used to responding to messages with whatever emoji fits my actual mood (big fan of and ), but in Teams you have to choose one of six for no obvious reason.

My understanding was that this generally improved a lot of indicators of personal and family well-being.

> others pirouetting in an almost rotisserie-esque spin.

This article had me in honest-to-god tears multiple times while still being informative and interesting. Good show.

Just want to say that your dedication to this project and to helping your users is phenomenal.

Ok MacOs (Chrome), I'll usually open View and hold down shift. 'Reload This Page' changes to 'Force Reload This Page' and I like the visual feedback that it's actually doing what I intend.

But what if they weren't? What if one could create something with similar destructive force with materials easily accessible, and the only hurdle is knowledge of how to do so?

It's honestly an interesting moral question.

It's always such a strange, bittersweet feeling when some long-running presence in your life like this comes to a conclusion. Though, I'll admit I've never had one running for a decade. Few years at the most.

100% same. I absolutely love programming, and enjoy my job at least 9 out of 10 days (though my current has a whole lot more meetings than I'd prefer.) I consider myself immensely lucky.

Super cool: security is such a fascinating field. One of the things I love about software is that there's _so many_ interesting and different directions one can go, depending on your own interests and predilections.

Either way though, security is incredibly important. You're doin' the lord's work.

So, I'm sure I've posted my relevant experience before and will likely post it again.

Graduated with a STEM (only partial comp-sci though) degree from a state school in NY. The uni prepared me zero for how to interview, as a result I bombed most of my coding ones (I remember being asked in one "Tell me about yourself", and having never heard of an elevator pitch before saying something like "Uhh, I think Buddhism is pretty cool..." and remember seeing the light go out of my interviewer's eyes.) Took some tech-adjacent contract jobs, and eventually ended up doing helpdesk for seven years.

Hated it, knew I wanted to program, eventually left my job to attempt solo Android development but had no idea how to manage my own time. Finally heard about coding bootcamps from the friend of a friend, did some research, and joined one (was lucky to have enough money saved for tuition, something like 15k.)

Was one of the only people in the cohort with any prior CS experience, but almost everybody was dedicated and did quite well. Was a great experience, though stressful (actually developed shingles midway through, which for someone in their early thirties generally indicates serious stress.) Graduated, and landed my first programming job in about three months.

It was hard, and my entire team was remote which wasn't great, as I didn't really feel empowered to ask as many questions as I should have (which is extremely important.) Was a great experience though, and everyone there was fantastic. Was downsized out after about 13 months, landed another job six months after, and stayed there for almost three years before we were acquired.

The tl;dr is that bootcamps worked amazingly well for me, and I've never been happier in my current job – it's night and day from what I was doing before, and pays a whole hell of a lot better. I keep hearing that the bootcamp ecosystem is different now, which is a damn shame because it worked a miracle for me. I was lucky too: our cohort lead instructor was a phenomenal teacher, which obviously isn't always the case. But it's a trade-type school which, in a perfect world, is available for people who want to attempt this transition.

Oh, my school also provided something invaluable (as is mentioned in the article): they hustled to connect me with companies looking to hire new devs. Both of my positions originated through connections my bootcamp made for me (I did a lot of work to land interviews myself, but both times ended up taking positions the bootcamp facilitated.) A really good business development department (or whatever they call it) is incredibly important in a bootcamp, imo.

I think I ran into a very similar issue recently too, stale closures right? didMount/willUnmount worked perfectly, but useEffect got screwy very fast, even posted a SO article trying to see the best workaround, nothing great.

Just want to add: you're lucky to have four months paternity, at least if you're in the US. Many companies provide far, far less, if any at all.

Over 900k dead in the US alone from covid. Sure, that's a minority, but can you really shrug your shoulders at that number and say it's just a minority, no big deal?

Nice Mitnick callback.

I went to Stuyvesant high school, and graduated in 2000. Stuy was a few blocks from the trade center, and I had friends who were still in high school that day. I knew people who saw the first plane fly in.

Was a bad day. There was a part of me that felt a weird guilt for not being there. Like, as a lifelong New Yorker, the trauma was part of my birthright somehow, and being away for school made me feel strangely removed when I felt like I should be feeling it in my bones.

My mother had PTSD for a good while afterward, and she lived way uptown from the trade center.

Was a bad day.

What if there's a Hindi who wants all beef to be outlawed in the US. Is that protected?

I find that pretty interesting. I've read a decent number of books of being lengths in my life; I'm no great reader, but I'm not a particular slouch either. And almost every book I've read I found very enjoyable; if I didn't, I usually put it down and not pick it up again.

But then, I tend to read stories by authors I already know I like, or those that are recommended or otherwise considered to be worthwhile reads.

Unfortunately that's behind a paywall.

Well, did we ever learn whether there were other planets in the system? It's been a minute and it's slipping my mind.

I really loved the entire trilogy though. Each book had a very different vibe and addressed a completely different topic/problem.

I will say, I think the one point in this article I disagree with is about finding answers on the internet. There are certainly been many times I've needed to dig into the source of something I'm working on, but much more often than not I've been able to find an exact (or close enough) answer with a couple of different Google searches.

Granted, this may be because the areas I work in are less technically complex than, say, writing low-level code or IoT instructions.

I have to say, I really love the back and forth between you and the various posters in this thread. Lots of good discussion and points being made, and reasonable compromises being agreed on - or even polite disagreement with thoughtful explanations why.

Any thoughts on Ruby? As someone who's worked with it a great deal of the time, I find it extremely simple and concise to write in.

Ouch. Well, never too late to take up piano or woodworking or something. After 40k hours of programming, rock climbing might be out though... your poor hands!

I got into programming at 14 because of writing scripts in Gemstone, a text based MMOMUD. Didn't even realize what I was doing was programming until college though...

My take is that step by step commented explanations make sense when it's something either extremely complicated or making use of a system or tech that's not widely known.

Otherwise, clearer code, smaller methods and better variable/method names are the way to go imo.

Another reasonable exception is referencing external sources - whether it's a specific library you borrowed code from, a piece of documentation needed to better understand what's going on, or a reference to a SO post explaining some weird workaround you've implemented.

Appreciate the clarification. Comments can (and are) definitely overused and abused, but they absolutely have their place.

While "if it ain't broke, don't fix it" is often a perfectly valid approach, there are going to be times when an upgrade can result in significant performance improvements or fewer admin headaches.

Not every OSS developer does, or wants to, request donations for their software.