tsewlliw

Expect a different title track, different comp ranges(it's likely in the project management job family, go compare on bls.gov), and likely a manager without experience in your new practice. If you're the first/only, you're also looking at making sure folks understands your role, and how to value your efforts.

I haven't seen folks make the change in formal role. I have seen folks take on the role, and I've taken it on myself (not my fave) with moderate success to make things happen.

Biggest advice: support the people in producing good outcomes, any processes should serve that. But the people create the outcomes, the process is a disposable tool.

Me! I'm working on myself as a physical machine that carries my experience through the world, and my ability to make that a fun and exciting journey full of connections, support, and joy.

Two things to consider:

1) If everyone else seems like a jerk, maybe you're the jerk. Hard for anyone here to know. I've been the jerk before, happens to all of us. Not everyone stops being the jerk.

2) Sounds like you don't vibe with the culture around feedback, and you're early career. Maybe look around seeking a strong culture of direct feedback as a positive thing you're seeking to help you grow. Seems like a great way to spend your questions at the end of a couple interview panels.

That product name needs some workshop time.

Would I as a 40 year old middle manager in Texas take a shot at living in rural central Europe for 4 months to work on ML for factory automation? Might feel lonely because I probably wouldn't move my family with me and take my kid out of school, but yes, that sounds like fun, like a great chapter in a life well lived.

Make friends. With friends you can make fun anywhere.

Tech debt either makes changes more expensive to implement, or adds operational work to your development team. The rest is bugs, features, and stuff you want to change. Addressing technical debt should result in the ability to make changes faster or make mores changes.

Which boss / coworkers / company did you vibe with?

You're missing that part where soft contribution is dropped. It's doing less work because the person aren't sharing skills and knowledge with the wider organization. That is valued work.

A witty saying proves nothing. -- Voltaire

Just as a general rule in conversation, invoking so-and-so's law or this fence isn't a productive tactic. Instead, ask the question that wisdom suggests you ask, and for this bothersome fence in particular, keep in mind that you are weighing an unidentified consequence against a proposed benefit, and at least endeavor to expend some of your own effort on suggesting what the value of the fence might be or how one might go about finding it. You may find some of that effort has been undertaken and that failure has not been shared.

Conceptually, this is rather like lossy compression with a shared dictionary. In practice your likeness has still been trasmitted. Jpeg files are after all just numbers too, merely less specialized.

Here's hoping we double down on Polio efforts and ensure it is entirely eliminated. Finishing is super important, and this milestone shows this is something humanity can finish.

This is probably decently efficient if you use recursive CTE's to traverse it, and use keyset pagination rather than limit/offset.

    with recursive cte (udo_id, prv, nxt, label) as (
        select * 
        from udo
        where udo_id = :first_item_id
        union all 
        select u.*
        from udo u
        join cte
        on u.prv = cte.udo_id
    ) select * from cte limit 100

> 3/ If you think your own DNS server is going to be better maintained than Google's, sure. But not everyone else would.

Be careful here, Google will rate limit you very severely and waiting 10s for DNS responses inside Nginx is no fun. Most cloud providers will give you a good resolver via DHCP that is much more forgiving when you accidentally abuse it.

Why does some software development take so little time?

My suggestion for the answer is that when the goal of the software project is selected carefully in the context of the surrounding ecosystem you can connect a few things and all the real magic was in picking the goal.

When instead you pick the goal and then figure out how to achieve it, who would be surprised that there is often more work involved after picking the goal?