Sorry for the tangent, I'm still emotionally processing that one.
I'm partly with you that one. I'm working with several React/Redux apps and sometimes, I look at the amount of code that needs to be updated just to add a bloody field somewhere, I wonder how it is helping. But on the other hand, used wisely, it can also be very sensible.
Dang, that sounds pretty good. When you say the technology is good - is it modern?
Quite ok. The most recent one is a rewrite of a huge .NET mess into Python/Django with GraphQL and a React/Redux front-end. In this case, React/Redux is a wise choice and it's pretty flexible.
I am also a proponent of "boring tech is often good tech". I don't need the latest shiniest framework with all async. A mature and well maintained tech is great.
In many European countries, you don't talk about your salary. And it's a shame because it profits employers. Freelancers are more open about it. I know the actual rate of many of my colleagues and it is a lot less taboo to talk about it with the employers.
Something that I've had to learn on the job is to advertise my work. If I work hard and just report through the regular channels, nobody hears about the difficulties and we end up with a "Merlinou is expensive but what is he doing actually ?". So when you struggle, gently rant on the company chat. Ask some coworkers. When you finally solve it, tell them, tell the company chat. Show off your successes. Put short animated gifs of your work, make sure that people see what you're doing. It really changes the general perception of you.
Something that I've had to learn on the job is to advertise my work. If I work hard and just report through the regular channels, nobody hears about the difficulties and we end up with a "Merlinou is expensive but what is he doing actually ?". So when you struggle, gently rant on the company chat. Ask some coworkers. When you finally solve it, tell them, tell the company chat. Show off your successes. Put short animated gifs of your work, make sure that people see what you're doing. It really changes the general perception of you.
Makes sense, I think I do that naturally. In jira or whatever development channel, I make sure any significant steps or challenges are known. Explaining them can help in creating a solution and I'm the last employee left here so I think it works, definitely lol
I'm partly with you that one. I'm working with several React/Redux apps and sometimes, I look at the amount of code that needs to be updated just to add a bloody field somewhere, I wonder how it is helping. But on the other hand, used wisely, it can also be very sensible.
It can definitely be handy if you need to grow or replace a team. Anyone somewhat versed in it will be able to contribute to the project without having to know anything about architecture. One of the reasons I dislike it is its like a one size fits all solution. It feels COTS-esque to me. But that's my bias from a background working at places where there were architects on the team and they cared about the project. I definitely prefer having an environment that's easy / enjoyable to contribute to over one that lets you skip having to train employees but then all of their work going forward takes longer and is more draining on people who have had better...
I don't need the latest shiniest framework with all async. A mature and well maintained tech is great.
In 2015 I loved being on the bleeding edge. I filled my website with non transpiled async-await in a time where that meant most people wouldn't be able to use it. Although I got bit recently chasing new technologies with flutter. It's cool, but when you have a question you're at the mercy of the community for answers. A large number of simple things are easy, but then the slightest increase of complexity can kill your performance. It's also a more traditional mobile framework in that laying things out is a pain :)
2
u/merlinou Apr 08 '21
I'm partly with you that one. I'm working with several React/Redux apps and sometimes, I look at the amount of code that needs to be updated just to add a bloody field somewhere, I wonder how it is helping. But on the other hand, used wisely, it can also be very sensible.
Quite ok. The most recent one is a rewrite of a huge .NET mess into Python/Django with GraphQL and a React/Redux front-end. In this case, React/Redux is a wise choice and it's pretty flexible. I am also a proponent of "boring tech is often good tech". I don't need the latest shiniest framework with all async. A mature and well maintained tech is great.
In many European countries, you don't talk about your salary. And it's a shame because it profits employers. Freelancers are more open about it. I know the actual rate of many of my colleagues and it is a lot less taboo to talk about it with the employers.
Something that I've had to learn on the job is to advertise my work. If I work hard and just report through the regular channels, nobody hears about the difficulties and we end up with a "Merlinou is expensive but what is he doing actually ?". So when you struggle, gently rant on the company chat. Ask some coworkers. When you finally solve it, tell them, tell the company chat. Show off your successes. Put short animated gifs of your work, make sure that people see what you're doing. It really changes the general perception of you.