Dolibarr for This, Dolibarr for That
This week we discuss DDOS attacks via Gitlab Servers, more cloud services being down, dolibarr and why every programmer aspires to be Linus Torvalds.
Intro
- GitLab servers are being exploited in DDoS attacks in excess of 1Tbps
- Google Cloud Down!
- You Can Be Directive Without Being a Jerk
When your team faces any hurdle or stuck moment, you’ll need to decide how to jump in. You might choose to adopt an empowering approach, viewing your role more as a facilitator and support structure as the team plots the path forward. But there will still likely be moments where you need to be directive, making decisions and tackling aspects of the work yourself. Don’t worry: we can still approach this in a way that drives buy-in and helps your teammates feel heard, and know they have autonomy.
When we as managers are being directive on a project, we’re deciding on the who, what, when, and how, and then we’re communicating that information to the rest of the team.
- Describe your role in outcomes, rather than describing how you’ll do your work. This way, the “how†can iterate over time, but your role’s success criteria remains the same.
There will be times when folks’ reactions will get in the way of that forward progress, though. When people are frustrated with being told what to do, they might slow down/fight/check out (which are classic signs of amygdala hijacking; no judgment here!).
Naturally, when you choose the directive route to assigning roles and responsibilities, there will be folks who aren’t thrilled about your decisions. That’s okay. It can be hard to remember, but you’re not optimizing for avoiding grumpiness here. Try spending five minutes to understand where they are coming from:
- What feels most important to you about this?
- What is your gut telling you?
- What one thing do you wish you could change about this?
By using a coaching approach here, you’re actually operating from the empowerment end of the spectrum. In a lot of directive settings, you will still have an opportunity to leverage empowering skills to help others feel seen and heard, and to help them grow. That’s why it’s important to continue adapting your approach as the context evolves!
But the bigger win? Asking these open questions and reflecting on what you heard them say will make your teammate feel heard and seen, which speeds up their ability to recover from their amygdala hijack.
News / Community Updates
OurCompose Developments
- How to pass raw tags to a Jekyll post
- How Cloud-Init can fail a deploy
- Dolibarr as an ERP
- Retire Instagram Account
Integration Discussion - Dolibarr - Overview
Grab Bag - All Programmers Aspire to Put Themselves in the Position of Linus Torvalds
Established Presence in a Large Project
- Large project benefits
- Established in market
- Established norms
- Work-life balance
- Established Presence benefits
- Know the project inside and out
- Being able to reference documented decisions
- Intimately familiar with the project
- You’re a guy from “that projectâ€
BDFL in a Project
- Respect
- Legacy
- Perks
- Opportunities
- Not-insignificant amount of money
- Proteges
- Right-hand men
- Support hierarcy
- Delegation of work and responsibilities
- Making decisions and setting policy
- e.g. “Do not break userspaceâ€
- like using CNAMES as workarounds
- document that as fix
- not tech debt - not making additional work
Tooling
- Hardest part about jumping into a project is figuring out how to set up a testing environment
- Tooling here can be anywhere from virtualenvs, to complex test suite, to production deployment
- Linus wrote his own toolset
- Miles ahead of market’s toolset
- Yes, I’m aware he’s not developing it now: “I maintained Git for six months, no more,â€
- Everyone writes glue code
- Yes, even in Ops and Infra
- Maturation process reduces glue code down to tool
- systemitize tool
- modular
- modern
- stable
- He took tool for highly successful project, and made that tool highly successful
- Delegated the maintenance of his tool to the FLOSS community
In Conclusion
What are developers looking to do
- Looking achieve long-running purpose that gives them meaning and successful work-life balance
- In a project that they are familiar with and scratches their particular itch which allows them a degree of authority
- Using the tools that they prefer and have crafted/tweaked/tailored to their own needs
In the future
- Web3 can lean even harder in this direction
- Linus doesn’t actually sell his infrastructure maintenance
- In the heyday of The SAFE Network, I got to ask ESR a question…
The tools we use to get it done
At Compositional Enterprises, we value our time as much as you do. That's why we only use the best Free, Libre, and Open Source tools to produce our quality content and products.
Take action and start using the same secure and convenient tools that we use by signing up for your OurCompose instance today! Invest in your community by donating directly to the podcast! Every bit (and byte) goes back into growing and spreading the show. Otherwise, to stay updated with the show and all future developments, find us on reddit or sign up for our mailing list using the form below!