Betrayed by github activity graph
-
@ben_lubar said in Betrayed by github activity graph:
@stillwater said in Betrayed by github activity graph:
@ben_lubar said in Betrayed by github activity graph:
other channels of communication
In a kinda way?
You want with a bunch of Inedo and DFHack people?
Does in DF involve braided carrots or gilded steam puddles?
-
@ben_lubar said in Betrayed by github activity graph:
You want with a bunch of Inedo and DFHack people?
Nope thread is
-
"Okay, I have a counter proposal for you. How about my assistant and I streamline the Project Management process by strategically engaging some recreational projectile modifiers amongst the current Project Management resource?"
"I think he's talking about hitting us with a bat of some sort," the lead PM murmurs to the Boss.
"..then implement an incentive-based contract revision process in a building resource free of distraction," I add.
"…torturing us in a basement," he translated.
"and round off the project by getting my assistant to reenergise the unusable resources at a non- strategic site resource," I conclude.
"..and then burn our bodies on some wasteland."
-
@ben_lubar said in Betrayed by github activity graph:
@stillwater said in Betrayed by github activity graph:
@ben_lubar said in Betrayed by github activity graph:
other channels of communication
In a kinda way?
You want with a bunch of Inedo and DFHack people?
The guy in the dog picture looked perfectly normal.
Ok, that's bordering on inappropriate.
-
@topspin said in Betrayed by github activity graph:
@The_Quiet_One said in Betrayed by github activity graph:
@cartman82 said in Betrayed by github activity graph:
@dcon said in Betrayed by github activity graph:
we know he wasn't writing and committing code for the job
No you don't. You only know he wasn't committing any.
If you write 2 days of code and don't commit, that's even worse than not writing at all.
Nonsense. I don't know if you're being hyperbolic or not, but while you should commit as often as possible, how could you say delaying your commits by a few days while actually working on shit is worse than not actually working on shit, especially if you're on your own long-term feature branch by yourself? That doesn't make any sense.
I'm pretty sure we have a forum member who argues you should get around 5 commits an hour.
Rookie numbers. I commit when I get to a sanish state. I tend to use git reset --hard as my undo button. I can end up north of 30 commits on topic branches before squashing them onto the named work branch. @cartman82 will never know how productive I can be on weekdays because of the squashing.
-
@pie_flavor said in Betrayed by github activity graph:
@cartman82 I just realized I should commit bugfixes on certain days so that the activity graph spells out 'deez nuts'.
i would go for "hello hr"