How does this differ from the <template> element?

@Tawzer glad to hear you’re doing better.
I wouldn’t worry about how you reacted given you reflected and noted it was due to being overworked. In those scenarios it’s pretty normal for people to get emotional. Whether that is via bursting into rage or crying.

IMO their response to your email was really unprofessional as well. It was condescending and uncalled for. People who act like that shouldn’t even be in such positions to begin with because their poor attitude leads to poor communication. Someone on their team probably didn’t loop them in on the change because they knew they’d be a dick about it.

@korrat haha wow. That doesn’t sound like it would make anything easier to understand.

Yeah fair point, I can see that being applicable on some slides. In this case though it already uses the words predecessor and successor so surely it could be rephrased.

Maybe I’m just being pedantic.

Just name the variable predecessor and successor? Like what do you gain from shortening it.

Damn that’s grim

I think it’s best to shift the way you view it.
You shouldn’t think of it as “my” code.
Try and detach yourself from it.

Also, maybe your colleague only realised there was a better way to do something once they saw your solution? A lot of the time your first solution won’t be perfect and it’s just natural to update it if a new requirement comes in, or if your touching that area of the codebase again.
It’s likely that your work led them to a better solution!

If it’s not clear why they refactored it then just ask. Come from a place of learning and self improvement. Just don’t take everything they say as gospel.
Sometimes they will have a lot of their own opinions in there, but it’s a good chance to see how other members of your team think.

Haha wow I didn’t know it was THAT bad.
From memory it also doesn’t trim whitespace from answers. So if you have a quiz with the question: what is 2+2?
And you enter 4 (with trailing whitespace) you get fucked.

Yeah I’d like to see what productive work can get done in 5 minutes between meetings...

Lmao chat is asynchronous, why the fuck would he be mad if it took you longer than 15 mins? If anything needed a response that urgently they can walk over and talk to you directly.

Like you said, take your breaks and tell him to fuck off.
I once worked somewhere where the PO would try and organise a meeting at lunch to “plan” some random story that came up.
I shut that shit down quickly. They’ll often try and manipulate you with shit like “be a team player”. Well, you’re being a team player by reminding them that devs are humans and need a fucking break so they can work in a healthy environment.

IMO it still has lessons that are very relevant today. Just like agile, people do it wrong.

@mt3o 100% this.
Never estimate time. Only estimate complexity.

Your boss sounds like an idiot. I’d be surprised if he actually ever programmed at all.

Rails monolith with some go microservices on the backend. React, JavaScript and Typescript on the frontend.
Yep I like it, it’s really productive to work in.

I hate the word “easy”.
In my opinion it should never be said when talking about dev work.
Often things will look easy but then you need to do some black magic to get the thing to work.
For example, styling checkboxes with css.

Man I’ve just been going through your rants and you have to put up with so much shit. Good job staying sane.
At least we can get a laugh out of it.

Beautiful.

Fuck me. People need to learn that sometimes this shit really isn’t that important. If it’s really that difficult to name it probably deserves a doc string or some comment.
What a waste of time.

@JohanO fuck man I know that feeling. Come in at 9am and by the time I’ve got enough information to actually action the ticket it’s time for lunch.
Like just provide some fucking context. It’s not that hard.

Safari might be shit but I’d still take it any day over the abomination that is IE

Yep sounds about right.
The way I’ve experienced this in the past is lots of unpaid overtime and managers/clients insisting we can’t launch without feature x.
Launch date comes around and there’s fuck all users.
People really need to learn to just chill the fuck out and tone down their expectations.

At a previous job Django admin was used for any CMS solution they could shoehorn it into.
It was painful. Custom widgets sucked.
Anything that was highly custom was easier built in a custom view. I think if you took that approach you’d be fine.

Just wow

@cafecortado we still use snow for our Christmas imagery even though it’s summer here

Yeah when this shit happens you need to educate them. Otherwise they will assume you’re the retarded one.

Sounds like a superhero origin story to me.

I’m starting to believe that they do understand and it’s all psychological to get you to work “harder”. In other words, like a slave.

Too bad if they don’t like code reviews. It’s part of the job.

My advice for this type of question is always “look at what language is used in the city you work in / want to work in”.
For example, ruby is super popular around me so it was the obvious choice.

@sidis405 I’m sorry for your suffering. May you find peace in 2018.

Lol he’s an idiot. Writing it in jquery will definitely avoid the need to migrate it later...

Not to mention Dota 2 helps with communication skills. If you can get four other retards to play the game without raging then you will have no trouble leading a team at work.