2,696 karma · joined October 29, 2012
Website: https://rietta.com/ Blog: https://rietta.com/blog/
[ my public key: https://keybase.io/rietta; my proof: https://keybase.io/rietta/sigs/uk2sEk4_TfZeNJ8ZwJN7VF1Ub-aLW_l8clAq-EbQ578 ]
I honestly have never heard anyone—even those executing it poorly—try to frame Servant Leadership the way the original author did here (the "curling parent" analogy).
I have certainly seen people fail badly at practicing this style, but that failure was invariably due to a lack of character, poor communication skills, or other individual execution matters, not an issue with the core concept of servant leadership itself.
The short take presented in the article doesn't match my lived experience with this style, both in secular and faith-based circles. The core idea is absolutely not that of a "curling parent." Instead, it embodies living the walk, walking the talk, and putting the team's needs before your own ego.
In fact, this profound concept goes all the way back to Jesus Christ, who modeled it by washing the feet of his disciples—a task reserved for the lowliest servant of the time. This act was deliberately shocking and context-defying. He effectively "turned the world upside down" by saying, "Anyone who wants to be first must be the very last, and the servant of all."
I'm not trying to proof-text, but this idea is ancient and deep. It's a profound leadership style that is unfortunately often executed poorly or misunderstood by modern practitioners. Poor execution doesn't invalidate the concept itself.
For everyone else, unless you use POP3 to download your email to your own personal device and remove it from the server, the email left on the server is not as protected under US law as emails that are fully downloaded to your device. The later requires a search warrant to acquire without your consent.
The same goes for communications on any social media or public forum, including discussions here on HN.
It seems that no evidence is a bit of hyperbole.
---
I'm writing to express my urgent concern regarding the negative impact of the 2022 Section 174 tax code changes on small businesses like mine. As owner of Rietta, Inc., a small cybersecurity firm, I still do much of the technical work. My wife and I have three young children under 6. My family and I have been directly negatively impacted by these changes from the 2017 act.
Previously, the tax code helped us afford open-source and experimental work that benefited customers. For example, modernizing applications to run on Docker improved testing and deployment. Our State government clients now benefit, but this was once experimental. Now we're largely back to just work-for-hire consulting, treated as cost of goods sold. I don't have the cash to pay for experimental software development only to then amortize it over five years. If I have $100k revenue and spend $100k, the current code allows only a $20k deduction. I owe taxes on the other $80k despite no cash or documented asset value. Experimental software doesn't work like that in this field.
I started this business 26 years ago. We provide important long-term custom programming and update work for private sector and State government clients ("STATE A" and "STATE B" judicial branches). Often, we work with code we didn't originally write.
As a professional computer scientist and business owner, I rely on my CPA for tax compliance. If I've erred in my example, that's on me. But I can tell you this amortization requirement particularly cripples small businesses like Rietta, Inc., where cash flow is critical, severely limiting the quality of services I can afford to provide. I support undoing this tax change.
One that I find regular use for when copy+paste does not work because I am either connected to a terminal emulation, vm, or something of the like is typeitforme. It takes the contents of a text file and sends them through the keyboard buffer after a few second delay (that allows me time to switch focus to the window I want the typing done).
I currently have it as a entry in my ~/.bash_aliasas file.
alias typeitforme='sleep 3 && xdotool type --file '
This works in stock Ubuntu Linux. You can check out the xdotool documentation for ideas how to refine it to do more.