204 karma · joined September 14, 2009
[ my public key: https://keybase.io/fernandobev; my proof: https://keybase.io/fernandobev/sigs/ tmRmp20apuPtwb9GIbZhtZlKZSWkK2I0TDX21oYGuwc ]
I've been thinking about all the reasons why I should not quit. The "freedom" in Academia, helping society (or a few people in it), the grass being greener on the other side, the pandemic is exacerbating my thoughts, it's just burnout, and so on.
I grow more convinced by the minute, particularly when I read that other share the same agonies (thanks for sharing this, author!). Industry is though in many aspects, but at least it's not a delusional bubble fueled by frustration as Academia is. If nothing else, Industry feels more real and with better chances of making me feel alive.
IMHO GitHub Actions is the flip switch here. Eventually it will become so useful and powerful that its advantages will overshadow any migration's cost related to tools like Jira.
- The pull request and code review UI are more user friendly. Everything I need is within reach and clearly visible (build status, test runs, change suggestions, discussions, etc). Gitlab has most of it, but Bitbucket is far behind on this.
- I spend a lot of my "open-source" time on GitHub, so the whole workflow/UI feels super natural to me.
- Issues can track tasks, Discussions can track talking. This is great to keep things organized.
- Great (and simple) release page (recently they added automatic changelog generation from merged PR, which makes it even better).
- GitHub Actions. This is a game changer. It is a well crafted, well documented way of implementing new things in the project workflow. Being able to use a "random" action someone put up that does what I need is priceless. It's like using open-source libs to enhance my code pipeline (allows reusability, discovery, etc). This is also great for CI/CD.
- GitHub projects beta has built-in support for sprints, as well as custom fields (integrated with issues, which is awesome). Everything seems to orbit around the code (imagine coding some custom GitHub action, whose code lives in the same repo as my project, which reacts to the content of a particular issue).
- Issues (and discussions) use markdown and can embed images, videos, spreadsheet, etc, very easily.
- will make developers happier (for me, GitHub is far superior than gitlab/bitbucket regarding tooling, e.g. actions, review, etc);
- is simpler to use, so it reduces management overhead;
- is friendly to non-dev teams, again reducing cooperation friction;
It will likely reduce costs overall. It might be by shipping faster (or better, or more robustly, or more homogeneously at least).
My personal take is that management people use Jira and alike because they read it is the "right" tool. Their motives might be weaker than you think.
Definitely give GitHub projects a go.
I see Serenity OS, I upvote it :)
As a side note: one of the project members was interviewed on The Changelog[0]. The interview presents many topics related to the project, e.g. technology, community, challenges.
[1] https://github.com/photopea/photopea/issues/45#issuecomment-...
I think reward boils down to the things you actually pursue and do, both in the academia or the industry.
I assume MIT is the right license.
You will not regret joining 1GAM.
I like to plan my actions methodically too, but sometimes I had to use 1GAM to develop my improvisation skills. When I was short in time and the month was about to end, I had to quickly come up with something before the deadline. That's when I had to prioritize the "get things done" instead of "plan the whole thing". I've learned a lot from it.
I wish you and your friend all the best regarding you game :)
Even when I had a clear vision of what I wanted to make, it was pretty hard to avoid feature creeping. When you hit the 90% completion mark, the TODO list starts to grow so scarily fast that the only way out is to develop/improve focus and the ability to ship things. That's when you level up as a developer :)
1GAM is a great opportunity to learn how to ship things, managing time and scope.
I'm sure I can find crappy Ruby/Lisp/whatever code and excellent PHP code out there. If you are a bad programmer, you write bad code. Of couse there are languages that try to prevent that forcing you to follow certain patterns, but it will not stop bad programmers.
I know PHP sucks sometimes, but it's still a cool language to play with.
About your (first) question, yes, they all execute scripts line-by-line.
I really got your point now. I thought about the "demoralising X empowering" and my solution for that was to work with pairs of students. Working as a team, they can discuss and motivate each other.
When I blog about the results, I will highlight the number of pairs that completed, partially completed and did not complete the assignment.
About the github idea, I like it, but my students are not familiar with git yet. I will try to blog about their main ideas and language syntax in the future.