Let's avoid magic strings too. 😀

forecast(WeatherType.Rain, 29);

@Michelle Yep, the pigeon was released without harm. A coworker was a bit freaked out when they were greeted by it though!

Valid point, but it serves as an opportunity to get up and gather informally to vent/rant which can help work out if there are wider problems to solve.

@julianmd yes, the simple command of 'npm i' downloads the entire internet at least twice.

Sounds like he will enjoy watching you sweat for a while before he returns fire. 📍

If you're working with passwords make sure you check out the haveibeenpwned API.

https://haveibeenpwned.com/API/v2

Yes, and I regularly do.

I have a fairly standard desk chair, but a https://eu.varidesk.com so I can regularly stand as I want. Takes about a second to adjust. Would very much recommend

@rEaL-jAsE how does it encourage bad design?

For me it has encouraged IoC, with highly testable classes that deal with specifically what they need to deal with. The class structure is well written, with clearly named methods etc, all refactored to maximise code reuse.

@fastbyte01 yep, very nice. Flow is a nice feature. Often want to bookmark things to read later at work or at home, flow is a nice way to do that.

Recently opera, but been giving Brave a try.

I have had well explained and researched questions needlessly down voted in the past, but in general I find SO useful and friendly.

@osiris1337 completely agree. It is important to be a team player and to be communicative.

It's just difficult in a busy environment when focus is so important to have people understand where conversations need to happen now, or could wait until later.

Everyone has different priorities at different times. Sometimes though, a bit more understanding of where other people are at, in that moment, would be good.

I like the idea of some sort of indicator, but you're right, it is open to abuse, which ultimately undermines the whole process.

Because they're all too busy coding to be out in real life.

Happy ranting!

Try to implement a more agile way of working. Get your velocity benchmarked, then when stuff must drop in, no problem, you just counter to say the other thing won't happen then.

Then people start to realise there is a real effect to squeezing things in, and leave it to someone else to establish which is priority. Something comes in, then something goes out. It's that simple, do not bend on that. It is not fair that you should suffer because someone else has made an ill informed promise.

Fine to do it on important stuff, as long as you have the time to fail and retry, but that's a rare thing.