do you guys think it's dangerous territory to do something you weren't asked to do at work? like, i know i can improve

Ranter

darksideofyay

5938

Comments

4

Voxera

11388

3y

That would depend all on the spirit on the work.

If they trust the devs it could be very appreciated but if they are controlling they probably will not like it since they will assume you did it instead of something they would have liked you to do.
1

TwentyMinuteMan

485

3y

Depends on your workplace but what you described is called “boy-scouting” some workplaces encourage it some boomer workplaces are against it
1

shovethisrant

5985

3y

As long as your able to convince management that it’s directly part of the solution then why not?
4

soull00t

1967

3y

"mask" it as "refactoring required to implement feature X / fix bug Y" if you need to touch this part of code (or related code) anyway...
some of my colleagues price in refactoring into their estimates by default.
or do you rather have major improvements in mind?
3

electrineer

29785

3y

Some things are just better to do and not ask.
2

EddieBro

121

3y

I'd say it's Ok when it is minor and involves your current working file.
Otherwise you should consider making a task / issue and let it be approved if you are lucky.
1

NoMad

13653

3y

I support doing it. How, I have no idea. I'm not exactly the politically correct type.

Edit: what I'm trying to say is that it seems to me to be the morally correct thing to do. But I'm unaware of how to do it to minimize obstacles.
1

whiskey0

885

2y

I remember I was hired as a react developer and the org I was working for needed someone to fill the gaps and help out with writing the backend code (c#). I said yes because I wanted to help the team out. Biggest mistake of my life
0

EddieBro

121

2y

@whiskey0 yep, don't go out of your territory. Even if you can help.
In the end you'll end up either with more stuff to do, or make someone not happy.

Add Comment

question