Tumblelog by Soup.io
Newer posts are loading.
You are at the newest post.
Click here to check if anything new just came in.

June 03 2017

roko
07:05
8144 c7c7 500
Reposted frompffft pffft

June 02 2017

roko
19:47
Reposted fromfungi fungi viaHereName HereName
roko
03:14
Reposted by919 919
roko
03:10

May 31 2017

16:23
roko
16:20
1272 39d3 500
Reposted fromRockYourMind RockYourMind vianaich naich

May 29 2017

roko
00:47
1618 848d
Reposted frompotatolovero potatolovero viadarthsadic darthsadic

May 28 2017

15:31
0166 8442 500

ghastly-h-crackers:

monkeyfrog:

merhaskell:

he’s got important capybara shit to do 

This photo makes me unreasonably happy.

I must go, my people need me.

Reposted fromfinnglas finnglas viamolotovcupcake molotovcupcake

May 27 2017

roko
05:03
6184 2c2a 500
Reposted fromacetylcoa acetylcoa viaznuh znuh
04:44
0310 ff5f 500
Reposted fromspookystyx spookystyx viabrightbyte brightbyte
roko
01:01
0112 ffa7 500
Reposted fromHereName HereName vianaich naich

May 25 2017

02:46

May 23 2017

roko
01:59
9981 86d3 500
I dare you
Reposted frompiehus piehus viaBanani Banani

May 22 2017

roko
14:55
9937 f5ad
Reposted frommoochava moochava viamalborghetto malborghetto

May 19 2017

roko
16:17
Reposted frompseikow pseikow
roko
16:11
6064 4051
Reposted frommachinae machinae
roko
15:11
Play fullscreen
Flawless Design - YouTube

May 17 2017

roko
17:55
9592 557b
Reposted fromTenSigis TenSigis viaFreXxX FreXxX
roko
17:46
Pivotal Tracker. It lasts for a long time, until the product outgrows it. As long as the team is small and lean, you won't have any issues, though.

What I definitely NOT recommend:
* Trac: Does the job, but the UX is terrible. Over-configuration quite likely, especially for small teams.
* Redmine: Same as Trac, but in Ruby instead of Python.
* JIRA: Once you join the dark side, there's no going back.
* Virtually every TODO SaaS: It doesn't work out. Things go stale. You'd have to do a pretty awesome job at onboarding the team to get it working. It's just too vague. Some I've tried and failed with are Wunderlist, Trello and Basecamp.

Generally:
* If your team is fully distributed, most of the tools I don't recommend might work, because they could be set up as the primary channel of communication. Once it has become the main way to communicate, it will work out, because all information is in one place, and the overhead of the tool can't be navigated around by means of personal communication.
* If the whole team is on site, just use damn post-it notes. It doesn't get any leaner. If you need a tool in addition to post-it notes, make sure to keep both in sync, or at least define the single source of truth.
* It's tempting for an engineer to create a really intricate workflow that covers all the bases. This will only tie you down in bureaucracy in reality. Spent as little time as possible on workflows, and let people improvise for edge cases. I presume you work with intelligent humans - they'll to the responsible thing.
* Define a single source of truth. The issue tracker should have precedence over coffee maker conversations, and coffee maker conversations that are actually relevant should be recorded in the issue tracker. If you look back at an issue in a year, you won't remember every decision you made in a conversation. Document the shit out of stuff.

Just some things I picked up over the years. Hope it helps.
Reposted fromsoba soba
Older posts are this way If this message doesn't go away, click anywhere on the page to continue loading posts.
Could not load more posts
Maybe Soup is currently being updated? I'll try again automatically in a few seconds...
Just a second, loading more posts...
You've reached the end.

Don't be the product, buy the product!

Schweinderl