jiraTicket said I assume it didn’t even cross their mind you could hear their machine

Kinda makes sense to run that stuff at night (if neighbours could not hear it),You should be happy they call it iPhone Air - rather than making EVERY iphone thinner.

Allthough I would be interested in an iPhone Phat - with a huge battery.,Did you learn anything about development philosophy or debugging strategies?,I would also consider this exact same rant would've been posted if DevRant would've been around when they switched from Iphone3GS to Iphone4

"Why make it thinner? Just keep it the same size and make the battery last longer"

Might be a constantly valid question though, just saying this is nothing new, just a continuation of thinnification going on for over a decade.,I rarely hear people imagine coding is easy

Most common thing I hear is people imagine that you build something once and then it's done an will last forever

"Isn't that website DONE?" 🤣 is a common question.

(But if we're honest, us devs might not be better, for example I've heard defvs say "I wonder what devs at Craigslist do - that site has not changed in years" but it is probably under constant development),I'm curious what you mean regarding implementing NPM.

Was this your first time using NPM? Did you use to have a ton of 3rd party scripts imported before - but now you tried importing them as packages for the first time?,Webpack can be notoriously complex though.

(It really depends - in some new projects I've managed to copy-paste another project's webpack config and just get stuff working asap, in other projects I've got stuck with Webpack issues for a long time),Consider giving your boss feedback in an structured way.

My team has recently been forced to take a class on how to give constructive feedback - so these would be my tips:

1. Ask if it's a good time (if they have a headache or personal problems, it's a bad time) "Hey, how are you doing? Would this be a good time to talk? I would like to give you some feedback"

2. Lay down the terms. For example  "I have some feedback regarding communication. I'll tell you how I feel about what I think is an issue. Then you can share your point of view and we can try to resolve it. OK?" 

3. Just tell em the issue straight up, from your perspective - including 1 recent example: "I feel like when I ask you questions - sometimes you respond without having read my question properly. For example the other day I asked about images that did NOT exist and you gave an answer about images that DID exist. Can we talk about this? Are you aware of this?",I've been involved in a situation like this. A dev lead from another team was writing really short and incomprehensible messages on slack.

A colleague in my team gave them feedback.

Got the response "Thanks for telling me! I was not aware it looked that bad. I admit I have a bad habit of replying to Slack questions really sloppily when I'm in meetings. I guess I imagine every question is super urgent. I will chill out and read questions properly in the future. Thanks again",Will the GUI remain the same?

That is: The way a user marks a spam post is to downvote and select ”offensive/spam” as the reason?

Cause I’m thinking: maybe the ”offensive/spam” label is too broad so it’s unreliable…if some users select it willy nilly for human posts which they just find annoying.

in that case if you wanna target bots specifically consider adding a separate category like ”suspected spam bot”. 

No idea if that IS an issue - just a suggestion if it would be the case 💪,@retoor oh sorry did not read OP properly```