Read on Twitter
-thread Ways to game development
they count LoC - if your work's based on an article, transclude the whole article in as a comment.
also - provide elaborate header comments
they count LoC - if your work's based on an article, transclude the whole article in as a comment.
also - provide elaborate header comments
If you have a particularly productive sprint/week/whatever stash the extra work. When you need to get real work done, dole this stuff out.
occasionally do something inefficiently. Now you have something you can do as 'performance improvement' by dropping in the obvious right thing.
on a team level - need to look productive but not much accomplished this release? Have the graphic artist make new icons, or change the theming.
Release 8.1.0 major release over 8.0 - no, it's 12 bug fixes, a minor improvement to a dialog box, and a new color scheme.
Release 8.1.0 major release over 8.0 - no, it's 12 bug fixes, a minor improvement to a dialog box, and a new color scheme.
If you need time to do a major bit of work on an engine, include some very visible thing with it to make the agile weenies happy - gives you a rug to sweep the real work under.
change in management is a great chance to dump your project in -
new manager: So what's the status?
me: I started working on <my toy project last manager rejected> a week ago.
new manager: So what's the status?
me: I started working on <my toy project last manager rejected> a week ago.
file trivial bugs.
Leave them set for a long time, then close them when you need time to actually work.
Leave them set for a long time, then close them when you need time to actually work.
Do that with a partner - I file bugs it's natural for Bob to close, and he does it for me. Deniability.
Similarly - have a partner you can signal when you need time. Then in next sprint meeting they buff the points on stories you're likely to get.
If you're in a brainless 'we don't do design' shop, use above tricks to make some time and make your own secret design doc. The architectural win gives you lots of extra time.
Have a semi-complicated manual task you have to perform manually at intervals? Use above tricks to grab some time and automate it. instead of reporting you've automated it, you now have a free block of time every time you have to do the 'manual' task.
have to write in some horror like JS or php? No, you only have to COMMIT in that. Write something sane that generates the horror and check it in.
building with no-code front end? leave it looking really crappy til the invisible back end work's done, or management will think it's 'mostly done'
conversely, want to avoid being cancelled? clean up the appearance of the UI, even if it's not connected to anything.
You all know any more of these?
Napkin LaF - Swing programmers got tired of this 'looks done' effect, made a look-and-feel that looked like it was drawn on a napkin. Until a piece was finished they used this LaF - like GAs putting DRAFT on placeholder art so it didn't end up in prod.
