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)

I was put off by rust after watching a stream (possibly theprimagen) where some rust dev was hacking along at speed and then had to stop after calling a function, saying something like ”oh, now I’m forced to explicitly handle potential errors from this call. Feels unnecessary. I wish it throw an error that was handled by some global/parent error handler, as you would in other langs like …JS”

No idea if that is accurate but sounded annoying as hell

I don’t worry about devs being replaced entirely

But I can see areas of dev work being replaced by ai - especially within rapid prototyping and mvp experiments

For example: let’s say a web site company wants to experiment with launching some new mvp thing ”just to see if it gains traction” and someone suggests launchkng ten simple games like snake and sudoku.

You could pay for a dev team to do that (massive cost - plus it might never be done since it’s a large investment thrown away if you decide to scrap everything)

Or you can have one dev spend a day, generate 10 games using AI, spend a few hours testing, soft launch, and see if anyone plays em - and if not, scrap them

Weird that random people with access to a tool can see anyone’s salary

But the concept of using consultants is common

I was a consultant for a few years - I didn’t get a high salary - but for the company that got a consultant dev the price was much higher than a regular employed dev

Are you sure the figures you see are what the consultants are making - or just the expense for the company

(The expense can be waaay higher than the salary - even for employees)

DateTime is one area where a lib is justified in most cases even if you’re usually a ”we don’t need a library for that” kind of dev 🥸

(PS: for all JS devs I’d just wanna mention I hope moment.js is dethroned and replaced with date-fns)

"A 13 represents a whole 2 week sprint. An 8 represents a week and a half."

🤣 Oh it's so laughable to see these insane systems people make up just to make story points abstract. With 13 points it would be 1.3 points per workday. With 8 points it's 1.0 or 1.1 point per workday.

Did someone enforce the Fibonacci numbers cause you had already bought Planning Poker card decks or configured your ticket system to only accept those numbers?

@ElectroArchiver "It's our customer's staff that's the problem , apparently the marketing team gave access to an external contractor"

Oh, damn. Dealing with 3rd parties (or... if a 3rd party hires a contractor... that's even further out 🤣) is the worst - everyone is unsure of who is allowed to lay down the law for them.

@BordedDev "only happened once in the ~5 years I have worked with him"

Oh! Then I'd say it's a non-issue 😊

(But this is a good example of the type of thing you might have to mention to people complaining about it. If I had recently joined your team as a dev and saw that everyone's editor were configured like this I would imagine this would be a huge potential risk. Before I was told people have used this for 5 years without issues)

…and as a follow-up: in my org we even have a recurring anonymous poll where people can answer if they feel stressed out about work. And if there’s a bad result - all teams have a talk about how no one should feel that way and if anyone wants to voice an opinion about why they feel stessed we could figure out how to reduce the stress.

(Some cynics will say ”anonymous? I doubt it!” but I believe it - we’ve had those talks in my team and everyone said they were fine - but still lead to a good talk over how to communicate to keep our team stress free)

@BordedDev "they have it as the default because most people don't care too much about the message"

What 😱 this sounds awful to me.

I don't care about commit messages being perfectly worded (I love squash-and-merge as the github setting) but I care about them not being entirely incorrect. I'm fine with poor commit messages like "h1" or "fix image" but I would be worried if there's a risk the message is "fix image" when they're working on a h1.

I'm kinda starting to think the PM was right to bring this up as an issue in the retro...

If this was my team I'd advocate for enforcing a setting where the commit message box was blank by default.

LOL, yeah you might be on to something.

The rudimentary simple code that you don't think much about is usually not something you vomit after seeing 6 months later.

It's often the "clever" and "innovative" stuff that you find revolting in hindsight.

Horrible. Sounds like it's time to have a "Team Rules"-talk.

Make it a rule that in editing prod manually is banned except for in rare extreme exceptions. Ensure that in order to be allowed to manually edit you must do something noticeable like post to a slack-channel named emergency-edits and say what you did. That'll at least alert all other devs something has been changed. And it'll keep people from doing it unnecessarily just cause they think "it's no big deal"

Seems to me that many open source contributors work too much in isolation

At work - if a dev has to do anything in our codebase for the first time - they’d get a walkthrough.

I would be kinda upset if I found out another dev studied a 2000 line file in my codebase (if I had such a thing) trying to figure it out on their own - so much time waste

Makes sense.

We’ve had people trying to do it 50-50 and they usually end up overwhelmed cause the PM role involves too many meetings

"squash and merge is enforced"

Wow. Then it's silly to bring that it up in a retro.

"intelij defaults to keeping the last message in the commit box"

Whoa, that sounds like a nightmare. Every time you make a commit in a scenario where you made a previous commit you'll have to clear the text box?

If so - I would make someone in the team spend 10 minutes looking for a setting that could change that. Unless you like it for some reason. Sounds like a potential source for future mistakes.

I also never had a PM who tries to have any detailed opinion about the code.

A rite of passage.

Where I'm from fucking up prod often just leads to improvements in procedure/testing/structure to prevent it from happening again. (But at the same time - we can't spend all our time making systems fully rigid - that would cost too much - a small prod failure usually is less costly than 2000 hours of dev time)

I always think we shouldn't blame an individual. If anyone part of our team did it - most of us could've done the same.

@dotenvironment I'm not sure how safe you feel within your team but if I was you I would mention that the way things are currently going you often feel stressed out. People may not realise that is how you feel - they might be trying to help.

We had a situation like that in my team: a guy from another team worked with my team 1 monday per week. He asked to be kept "in the loop and make sure I got some stuff to look at for monday" - we interpreted that as he would appreciate us mentioning him in a few interesting slack threads during the week that he could look at later.

But on monday we found out he had been stressed out and interpreted that as we demanded him to read these slack threads instantly. And he was a Slack-noob so he had a hard time keeping track of old messages, so he'd prefer if we waited until monday before we mentioned him.

So one example where people around you might seem like they're rushing you - but they didn't mean it that way. Where a talk is needed.

I kinda have a hard time judging this because in Sweden we generally don't judge dev performance in any strict way.

I'd say jokes about giving people a worse rating or ruining their holiday can be okay. In a team with a very relaxed culture where hard work, performance, etc is never brought up. (or example: in my team we do joke about shit like that but we have worked together for years and someone can say "I didn't get anything done this week" and that's 100% fine. It would not be fine if we started measuring performance for real, and people were stressed out.

Also: What is TT?

@Lensflare So true!

In my org the designers used to be theoretically aware of stuff like WCAG color contrasts, but often ended up ignoring them when they had an idea that looked great in low contrast.

They were very unaware of screen-readers etc and didn't really take it serious when one developer complained some of their solutions weren't accessible.

But then we hired a new designer that was more into that stuff and started doing presentations on it - the designers took it more seriously. And started adding color contrast checkers to their toolkits, and started asking us devs "will this be accessible" before doing a wild new design :)

Whether or not you need manual checks kinda depends on how you built the cron-job

For example: if a cron-job only sends an email "alert! something is wrong" when there's an issue - and you haven't got any such emails for +1 week then you can't be sure if the cron job is functioning or has stopped running.

But if your cron-job sends a "everything was fine this week" you can safely assume it's up and running.

@Demolishun LOL maybe!

I'm personally not seeing a "report spam" button though, maybe I just haven't looked closely enough or maybe I'm not a "trusted user" cause I've been inactive for months before yesterday

I'm bummed that streaming services haven't started betting on this.

I just watched some Youtube Short of Scorsese and DiCaprio talking about the 6 films they've done together and I would've loved if Netflix had dedicated an entire page to Shutter Island Extras.

I would totally watch a film like that for the 9th time if it for example had pauses where Marty and Leo talked about the process.

One idea for how to handle spam-reports on forums:

1. Add a "report spam"-button

2. When a "trusted user" (accounts that are a few years old that have some good posts) uses that button - automatically downrank that post and add a "suspected spam" tag to it.

3. If a "trusted user" abuses their power they lose it

Haven't thought it through so maybe it wouldn't hold up.

And not sure how actively devRant is developed or managed...

@Lensflare ah in some of those cases I would kinda partially blame the devs for not pushing for accessibility. To some extent I feel that's on us.

I kinda expect the average designer doesn't know as much about keyboard navigation and screen-readers as web devs. So it ends up being our job to educate them and push for accessible solutions.

I just listened to a good podcast where an accessibility expert says they kinda expect devs to spend time under the radar to handle accessibility if the org doesn't care about it

https://syntax.fm/show/836/...

Never really used Tailwind so can't say I hate it - but I can say it doesn't appeal to me at a surface level.

I'm used to one or two classNames, not dozens.

The code example written above me looks too much line inline CSS to me.

`div class="grid grid-cols-3 gap-4"`

just looks like

`div style="display: grid; grid-template-columns: auto auto auto; gap: var(--gap) * 4)`

You think developers are in charge of user interfaces?

They are often just forced to implement the UX/Design departments latest desires.

A) are these devs or other roles?

B) are your messages longer than 3 sentences?

I personally find at my company most devs are good at Slack (or equivalent work chat) but some other roles - like sales and design are awful at it, cause they usually don't communicate among themselves mainly via text - and when they do talk about tech stuff they get very uncertain cause they imagine they don't know the terminology so they'll ask every question again in a rephrased way.

(This shouldn't be an excuse - they should be able to handle it as they work for a tech company 🤷 but it's what I've experienced)

Not familiar with this - what dies an automated interview entail? Just forms?

100% agree with @devJs

x is good for oneline Array-functions.

Especially in code where you write a lot of that stuff.
I find that over time, if I name these variables something specific I end up regretting it and changing to x when I need more of the same code

Like if start with

activeUsers = users.filter(user => user.isActive)

And then I wanna do the same for an array of admins, which have the same props as users

Then I often change it to

activeUsers = users.filter(x => x.isActive)
activeAdmins = admins.filter(x => x.isActive)