@locksmithPrime@rakyll @dustinmoris @bertjwregeer If a company is not willing to pay what you are worth, i.e. taking advantage of you or the situation you are in, why would you stay in that company? Counter offers can backfire as well
@GergelyOrosz 3. Solution was to allow self management and add controls before and after deployment in combination with knowledge sharing sessions and documentation. Fundamental to work with good products and platforms, or the whole "castle" crumbles and the Platform team gets all the blame
@GergelyOrosz 2. One of the greatest thing my team has done is to allow Self-Service with guardrails. We started small and we were able to deal with requests. After a while many teams wanted to use the clouds and we were also not happy to deal with IAM (example) and it became slow and tedious
@GergelyOrosz <- platform team lead in large org. 1. It becomes detrimental when it becomes another blocking gate when not involved in early talks about arch with project teams. Devs not informed about any laws, best practices (ex. avoid TLS 1.0), system architectures, ...
@Lemonjet@dummdida here it is for everyone: https://t.co/S7JtN81jdP
P.S.: great job !
May I ask how you run Prometheus to secure the communications? https://t.co/1nOXStOPtN
@gr1m0@balbuenac@GergelyOrosz Very interesting) If I understand well, the new service uses different columns and iterates over each record to migrate the old data in the new columns.
Is this done for specific columns? Any risks associated with the new microservice not finding some data it needs?
@GergelyOrosz Likewise! I would never be where I am today, if some managers did not bet on me. I have interviewed 5 candidates the past week, and there are two which I want to bet, but I cannot hire both of them 😭
@GergelyOrosz 5) Dictatorship. Lead who takes decisions without listening and discussing with his or other teams impacted by his decision. I have many times how much frustrating it is and the bad effect on the motivation even of the highly committed people.
@GergelyOrosz I have seen many bad traits:
1) Lack of communication. Engineers, especially junior ones, need to be informed of what's coming or decisions taken between managers. Engineers have not telepathy to know what has been decided in their absence and expect to be aware
@GergelyOrosz 4) Fearful of the team. As a lead, you are supposed to take decisions your team may not be comfortable with. Such as abandon the old ways and embark in new paths.
@GergelyOrosz 3) Unable to understand. An engineer lead / team lead must understand what his team speaks or complains about. When he doesn't know, he must make the effort to understand/study what's necessary. Decisions taken in the dark can have a catastrophic effect in the medium/long run.
@GergelyOrosz 2) Poor planning / prioritization. A lot of companies chat how much agile they are and use it as an excuse to not plan activities. Nothing worse to be constantly interrupted and leave things incompleted. Then these accumulate over time and become the next emergency.