21–30 of 136 posts
I've been tech lead at different companies. Every time I switched companies, I started out as senior dev and got promoted into the team lead role again; each time with full support of my team. I don't look or act like a leader and this has been a hurdle for me. But what typically happens anyway is; within a few months, my code ends up being a core part of the project; my modules become heavily depended upon and someh…
That Spotify squad tribe diagram makes me want to vomit.
Honestly, the more I look at it, the worse it gets.
> After that incident, I created an incident review document and suggested a small review of the tasks that should be prioritized to prevent it from happening again. I got carried away and created an initial presentation for the other backend Chapter Leads with a backend strategy. I do not remember it perfectly, but it included hexagonal architecture, a testing pyramid with contract tests to avoid breaking APIs used…
> hexagonal architecture God help me. Was on a project where this was used to justify so much extra boilerplate. Every class had an interface, and then we used dependency injection to supply the class to something expecting that interface. Actually, it was in Rust, so there were no classes, but that didn't stop us. Absolute waste of time.
I've been tech lead at different companies. Every time I switched companies, I started out as senior dev and got promoted into the team lead role again; each time with full support of my team. I don't look or act like a leader and this has been a hurdle for me. But what typically happens anyway is; within a few months, my code ends up being a core part of the project; my modules become heavily depended upon and someh…
I don't understand the point of your comment. Why did you switch companies?
"I'm a tech lead, nobody listens"... 1. Listen to what other people say and what they think the problem is, or what the problem "says". 2. Think, ask questions to clarify and repeat step 1. Is the problem actually technical? branch a. otherwise branch b. a. have you considered the problem is mostly not technical? then proceed to branch b. b. what miscommunications are keeping the solution from being implemented? 3. C…
I think its important to note in most companies I worked in, the issues were mostly political.
I've been tech lead at different companies. Every time I switched companies, I started out as senior dev and got promoted into the team lead role again; each time with full support of my team. I don't look or act like a leader and this has been a hurdle for me. But what typically happens anyway is; within a few months, my code ends up being a core part of the project; my modules become heavily depended upon and someh…
I don't understand the point of your comment. Why did you switch companies?
> After that incident, I created an incident review document and suggested a small review of the tasks that should be prioritized to prevent it from happening again. I got carried away and created an initial presentation for the other backend Chapter Leads with a backend strategy. I do not remember it perfectly, but it included hexagonal architecture, a testing pyramid with contract tests to avoid breaking APIs used…
This is probably the single, most important advice for any new person joining a company in a (technical) leadership position. There are going to be missing things in any org, and bad mistakes, and people needing to learn new things. But also there are going to be tons of decisions that make "no sense" on first look that do have a reason behind, and to fix that "root cause" you probably need a 3 years plan and buy-in from C-level. So, trust the team you are going to lead.
At previous corporation, the tech lead simply recommended for sackings a developer who was questioning his approach. Once he got sacked, everyone listened... ...and then most of best skilled people left in the following weeks. Tech lead then hired his mates and company nose dived.
- I was trying to figure out who have access to domain X? It is not on AWS and by whois it is under some random registrar in Europe. I got just shrug from boss. Everything works so why bother?
- After 3 years of scratching my head and try to repeatedly get it to attention we finally lost the domain (card probably expired), everyone is panicking, because emails has stopped working, so email based 2FA are not working either which has cascading impact on all services. And I am just raging in my office because I was trying to prevent this situation for 3 years to no avail.
- The European registrar did not cooperate at all. We have offered them good chunk of money, no response (weird?), eventually domain got moved around and reregistered by various bots and domain companies and I was able to get it again via domain backorder.
I have left shortly after because this was just ridiculous lack of care with good amount of reactive behavior as a cherry on the top. My take away from this is that you can't change the culture. If top is bunch of sloppy clowns, whole company is going to be the same.