jordanbeiber

12 ms·

61.
by jordanbeiber 4y ago
If they still use cadence/temporal[0] extensively this kind of blurs the concept of technical ”services”. We’ve started to use it (temporal) a bit for general automations, and it’s pretty great. Monorepo with a lot of different activit
62.
by jordanbeiber 4y ago
No hypervisor for cgroups (docker & friends), no. Which is why something like LXD/LXC outperforms hypervisor virtualization by quite a bit. I was on a team that ran performance critical stuff for a reasonable sized ecommerce busine
63.
by jordanbeiber 4y ago
Conways law. The teams and management structure will immediately become a technical debt. If we let the product ”decide” where boundaries actually exist and team up accordingly there’s a chance to scale and maintain a bit of velocity. It re
64.
by jordanbeiber 4y ago
A couple of times a year, this is acceptable to me. I have taken my kia e-niro on 1000km roundtrips, and this is totally acceptable as you have to stop for at least one meal, possibly two. The convenience of an EV is fantastic - but I’m luc
65.
by jordanbeiber 4y ago
An EV can probably cover 99,9% of trips made in densely populated areas. Very few trips are 350km roundtrip. I’ve had EV’s for the past four years and we rent an ICE when we’re going on ski trips and such. The continued saving on gas more t
66.
by jordanbeiber 4y ago
Take one full day every other week where you play around, learn and explore. If you have not been able to do this at least 5 times last quarter - why not? What can we do to allow for that to happen. This is an example of an actual goal I ha
67.
by jordanbeiber 4y ago
Retros can be great though, to be fair. If approached as a way to adapt ways of working - e.g ”we’ve had to many pointless meetings that could have been asynchronous slack messages.”
68.
by jordanbeiber 4y ago
We’ve started to do this when it comes to stuff that is architechtural significant, for example team A decides to event-source foo. Or team B opts to write microservices. Also - anything infosec related goes through an ADR process. Rule of
69.
by jordanbeiber 4y ago
Configuration of applications are usually exposed as properties by package maintainers. What I like about nix is the complete ”as code” approach - I usually look in the the package repo for the properties. A couple of times I’ve had to esca
70.
by jordanbeiber 4y ago
I probably appeals most to developers as sharing application development environments with shell nix files is totally awesome. I must say that using nix on my primary workstation makes it feel like an appliance. The system generation roll-b
71.
by jordanbeiber 5y ago
I’m gonna be THIS guy, though: first - there’s more to our environment than co2. Prolonging life and reducing negative health impacts are another bonus. Yes, there is still an environmental cost of the production of EVs but these vehicles d
72.
by jordanbeiber 5y ago
Interesting read - I love questioning “the process” and drilling down in ways of working. I am, almost an involuntary, manager of 6 different dev teams, and I often say that my aim to reduce the “management” part of my job to a shared dutie
73.
by jordanbeiber 5y ago
Seems like your place of employment have a bunch of cultural and work process issues to sort out, to be honest. The diary entries are supposed to replace other forms of communication - not be an addition. My place of work strive for autonom
74.
by jordanbeiber 5y ago
> Waste of time unless you’re an obsessive micromanager. Other team members either don’t read these entirely or just skim them. This is probably true if you work in complete isolation. If, however, you are a part of a larger team or orga
75.
by jordanbeiber 5y ago
It’s just bad practice having accounts scattered through bunches of systems that shouldn’t be used anymore. It’s often a licensing issue, and definitely a security issue. Either you maintain this manually - proper time consuming chore at la
76.
by jordanbeiber 5y ago
In, for example, an enterprise setting you rarely want individually clever and creative solutions. You generally want domain expertise shared in a team, and continuously molded to perfection over time. Mobs and pairs can really shine here,
77.
by jordanbeiber 5y ago
Yes, I’t a matter of perspective I guess. Having managed many thousands of hosts over the years, I’ve longed for something like nixos. Managing largeish scale infra is not what I do these days, but nixos still appeals to me, and I use it fo
78.
by jordanbeiber 5y ago
Linux, niche?! Idk where you’ve been, but Linux is ubiquitous and runs everywhere. It’s about scale mainly. A nixos host can be viewed as a solid state environment, in some respects. At least from a systems management perspective. If you sc
79.
by jordanbeiber 5y ago
Resource optimization vs. Flow. It all comes down to measuring outcomes over time. Doing agile is doing right-ish things at the right-ish times, including ways of working. Use retros - are we being efficient over time? Why and when? Why not
80.
by jordanbeiber 5y ago
About Phelps - he need to build, maintain and condition a whole lot of muscle mass. He’s incredibly far from a normal human - he’s a true specialist. Lots more energy goes in to that, compared to losing excess fat and living a “normal” huma
81.
by jordanbeiber 5y ago
I think a good way is to take any chance to move around. Ido Portal, for all his eccentric weirdness, knows things: > The body will become better at whatever you do, or don’t do. If you don’t move, your body will make you better at not m
82.
by jordanbeiber 5y ago
Having practiced submission wrestling and bjj for years - it is incredible strenous and requires conditioning to handle at all. Judo, with it’s focus on grappling standing up is ridiculously hard on the body, and is not something you just p
83.
by jordanbeiber 5y ago
Joel Spolsky from 20 years ago: https://www.joelonsoftware.com/2000/04/06/things-you-should-... Very good post, that holds a lot of experience. Unfortunately these things have to blow up in your own face, oft
84.
by jordanbeiber 5y ago
Building new things is seen as business risk, I reckon. This is why startups or VC backed things can explode, and innovate, but once you IPO, innovation is not what’s important - it’s about perspective I guess. When the death spiral of anti
85.
by jordanbeiber 5y ago
Having worked quite a bit with no/low-code abstractions and “workflow automations” I’ve seen a few problems arising over and over: - ownership and its boundaries becomes blurred - maintainability over time - lack of systems thinking an
86.
by jordanbeiber 5y ago
Broken processes and missing self-service, as you point out, is why creating a platform team is important for these types of places. They might not know it yet, although some are trying. It doesn’t make the infra technology more or less int
87.
by jordanbeiber 5y ago
Last couple of places we’ve called it “dev platform” or “dev tooling” team. I use to say that it’s like one of the business domain development teams, it’s just that the domain is “dev”. The businesses devs are the stakeholders, and the tool
88.
by jordanbeiber 5y ago
Yes, many enterprise devs I know are completely uninterested in infrastructure. This is also a great way of scaling teams - keeping a path of least resistance that is secure and compliant while giving observability and conventions.
89.
by jordanbeiber 5y ago
Couldn’t agree more. Plowing through this atm, about 10 months in… In my experience, layers love to get intertwined in, so called, standard systems. You end up with a business not really in control of its processes and developers who are ex
90.
by jordanbeiber 5y ago
This is why self-leadship is vital to “agility” - individual interaction before process and tools. Someone wrote, perhaps Tom DiMarco: “a process is per definition not agile”.

More ›