i run a free, anonymous audio host https://some.audio so if you need a place to host some audio, it's a good one! it doesn't track you, link back to your social media accounts, cost money, run ads, or anything. just hosts audio files. check it out, it's really not bad!
I'm slowly fleshing this page out with goals and stuff! Not really sure how to beg for money to support doing open source software (which I probably spend almost as much time on as my day job) in a socially acceptable way but I'm learning! https://www.patreon.com/zacanger
(i already published a package to npm and started the project, then found klaus, which is more or less what i wanted, but, whoops, too late, i already decided to write my own) https://github.com/zacanger/gwn
https://www.dailymotion.com/video/x79u0xa i watched all 4 episodes (split into 8 half hour blocks) of this today, because i of course want to support yves, but then i ended up laughing and crying a bit. this should be a whole series, it was so good.
Did you know, `ds` is now installable with yaourt/yay/[whatever Arch package manager is cool this week], and also with Brew? It's true, you can do that now!
@ceejbot you are so on top of these PRs, like a merging ninja
i'm now fortunate to be on a team that loosely does kanban rather than scrum, so our main concerns are:
* is work flowing in?
* is work flowing out?
* is anyone blocked?
* is anyone overburdened?
* are we doing work that helps achieve our higher-level goals (as laid out on a flexible year-long roadmap)?
and that is just so lovely. but the rest of the department is still very much in the "jira charts and scrum masters are our lord and savior" mentality, & my team is part of the department. so.
@zacanger Agile™ and Scrum™ are now tools for project managers to micromanage, and no longer about the initial concept of agile programming. The idea *was* to get tight feedback loops with the users of your work, not to make freakin' burndown charts.
also while i'm at it:
points systems separated from estimated time spent are a lie, everyone ties them back to time in some way or another no matter how much you try to abstract that.
fibonacci point systems don't make sense to anyone and you'll spend more time bickering about what a "5" means than actually planning your spring.
just use "small" "medium" and "large," agree on roughly how much time one person on your team needs for each of those, and be done with it.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!