Worked at a web property that took scrum, used it and found it lacking in certain cases for development. They Extend it And called the new creation beyond scrum, abbreviated as BS snickers.
Unrelated to the shortcomings
we found that Scrumm with the timeboxing concept did not work for infrastructure teams.
You cannot just time box most Infrastructure task and just ship whatever you have when you exceeded your initially planned timeframe.
We came up with Kanban as a way to document progress. The swimming lanes together with a limit on things that can be simultaneously in flight served to mirror reality as an operational team much better than pure Scrum.
Southwest Airlines Flight 1380 was a Boeing 737-700 that experienced an uncontained engine failure[a] in the left CFM56-7B engine after departing from New York–LaGuardia Airport en route to Dallas Love Field on April 17, 2018. […] One passenger was partially ejected from the aircraft and sustained fatal injuries[…]
If the person on the phone had said “Capone, Al” instead of “Uh…” he’d possibly not gone to jail.
Even ill gotten gains are taxable and the theory of one crime at a time suggests that even “other, unspecified” could be with paying taxes on to reduce the likelyhood of successful criminal persecution.
There are reasons for tools like https://github.com/ixs/kvm-cli. It seems like every operations team built their own version that logs into the web interfaces, downloads the java stuff and then runs it locally...
I was just fiddling around with a SuperMicro X8 IPMI the other day. The X8 IPMI stuff is terrible, e.g. the warning that your Java installation is outdated on opening the website etc.
Turns out, you can actually install X9 IPMI firmware on X8 boards as the platform files are still shipped.
Might be worth checking out, if this improves things for you. It did for me.
Check out https://github.com/devicenull/ipmi_firmware_tools for unpacking (and repacking) the SuperMicro firmware. The developer just merged my patches making it work with some of the X8 boards.
As long as your board is listed in /etc/defaults of the IPMI tree you should be good.
The distance from Paris to Berlin is longer than Berlin to Lviv in Ukraine. Something that is often forgotten it seems.
The European Union has legitimate territorial security interests and a expansionist empire right next door that is encroaching on your borders isn't something the EU leadership likes to have around.
Considering that I doubt passively waiting for Ukraine to fall was never on the menu. Instead I expect the military and financial help for Ukraine to further increase as it is way cheaper to finance someone else to fight the empire next door than having to beef up your own border security.
There are certainly enough useful idiots around that are clamoring for cheap gas at any price but I do not have the impression that they get a lot of traction.
I saw some numbers the other day that 70% of the German population agrees that supporting Ukraine is important, even if it means higher energy prices/colder times in winter. Only the voters of the far right party AfD thought it a sensible policy to drop Ukraine. Not surprising really for Moscow's fifth column.
I previously used MiniKeepass which has been shut down.
My grated to KyPass, which looks good on paper but syncing with Google Drive didn’t work in practice.
Now using KeePassium Pro. Very happy. Does everything I need, uses the file API for opening files and integrates well.
Much wider hardware support with OpenWRT. If the hardware is accessible and supports Linux, there is an OpenWRT target for it.
There’s even a x86 and a raspberry target.
If you’re happy with DD-WRT, no pressing need to change it.
But if you want more features or specific packages, OpenWRT is the thing to look at.
What I find so baffling is that these experiences do not match my own atall.
I've been running a non-profit ISP for about 23 years with a few friends. We've always been doing this from our own IP Space (/20) in RIPE.
Even when we had problems sending spam (compromised user accounts, compromised php websites) and we ended up on a blacklist, we usually could get removed pretty fast.
For a few years our mail system would sometimes generate late-bounces, that is accept a mail on the incoming MX only to then figure out that it actually cannot be delivered later on and generate a delivery failure notification mail.
Not a good situation.
That got us into some trouble here and there. But even that could easily be unblocked again.
When we finally managed to set up a new mail infrastructure (2 year project cause it's a hobby) we set up new outgoing SMTP servers which cycle through multiple IP addresses. There was exactly one ISP (Deutsche Telekom T-Online) that was not accepting mail from some of these IPs. One mail and a turnaround time of abour 12hrs later this was fixed.
Gmail or Hotmail/live.com/Outlook never had any problems with deliverability. Even with a few users forwarding all their email to their gmail accounts including the spam that slips through our filters.
That might mean that a single mail would not be deliverd, but other users never suffered as our outgoing IPs are not being blanket-banned.
There's one residential ADSL provider that has a blanket ban on one of our outgoing IPs. There's no way to get that resolved because their mail infrastructure is unmaintained and nobody is reading their mail. Common problem with that one ADSL provider, googling their name shows other people have the same problem. shrug We just use a different outgoing IP for them.
No DMARK or DKIM setup at all for outgoing mail.
So I wonder, what really makes the difference in experience? Is it just the fact that we have a decent sized IPv4 Network in our name as PI space?
Unrelated to the shortcomings we found that Scrumm with the timeboxing concept did not work for infrastructure teams. You cannot just time box most Infrastructure task and just ship whatever you have when you exceeded your initially planned timeframe.
We came up with Kanban as a way to document progress. The swimming lanes together with a limit on things that can be simultaneously in flight served to mirror reality as an operational team much better than pure Scrum.