700 karma · joined November 5, 2010
All others stuff (CI/CD workflows, linters, formatters, code of conduct, funding, issue and PR automation, dependency bots, ...) moved to .github.
Now I have a clean and tidy Python project with a tiny 12-items root directory: https://github.com/kdeldycke/meta-package-manager
Source: https://twitter.com/kdeldycke/status/830035138805428224
I just added your contribution to my collection of resources on cloud billing: https://github.com/kdeldycke/awesome-billing/commit/df095efa...
An up to date revision of the site is available at: https://radiooooo.app
Here's a little helper script to listen Radiooooo from the command line: https://github.com/vikbez/radiooooo-cli
Most ERP projects fail. They end up over-budget and delivered really late.
Why? They are sold like custom implementations, promising the stakeholders they’ll be adapted to their specific needs. It's rarely the case. The reality requires the whole business to change: its processes, its workflows, its traditions.
Therefore, only companies flexible enough can survive such deep transformations. Companies that are agile.
Biggest lesson learned: you're no longer the decision-maker on your technical stack. Your team is responsible. Still, you’re liable for the result and its impact on business. That duality is hard to reconcile for former engineer. The solution? Build a culture. Better: create the conditions for a sustainable culture to emerge and persist.
That insight, and many other advices for new managers are compiled at: https://github.com/kdeldycke/awesome-management
TL;DR: don't.
This happened in a very early stage, self-founded startup in France (was the third person to join). Took me time to realize the situation was really bad and unescapable: I was young and lacking experience.
To employees: don't wait to be fired or to reach your breaking point. You're on the way to serious burnout. There is something out there called the market that is redistributing talents. So get out.
To managers: don’t be that boss.
The concept seems to originate from Netscape's CEO and the acronym exists since 2006, according HiPPO FAQ: http://bitly.com/HIPPOExplained
I kept a detailed list of all the things you needs to keep track of at https://github.com/kdeldycke/awesome-billing , and indeed, it's glorious.
We're currently in Phase 1 of the project. Which is all about collecting, in the wild, instances of this trending writing style.
Now if it get traction and grows out of a gimmick, and if Falsehoods articles become a new literary form in its own right, then maybe we'll have enough resources in the community to start Phase 2. Which might see more curation happens, as well as writing guidelines and add more structure.