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

May 26 2017

come to daddy
Reposted fromlaserpony laserpony viarunkenstein runkenstein
9195 077c 500
Reposted fromswissfondue swissfondue viarunkenstein runkenstein
7743 f9e3
Reposted fromparkaboy parkaboy viabrightbyte brightbyte
0307 47df
Reposted fromkrzysk krzysk viabrightbyte brightbyte
8961 0c14
Reposted fromjestemzero jestemzero viabrightbyte brightbyte
Reposted frombestform bestform viarunkenstein runkenstein

May 24 2017

Watch out with MEMRI content though. it may be (sometimes very) biased.
Reposted from3ch0 3ch0 viac-z c-z
5286 331e 500


I love the use of the word “arrives” like it was expected yet also somewhat feared

May 23 2017

2571 07c0
Reposted fromkaesekuchen kaesekuchen viajanuschytrus januschytrus
4676 c722

Tick-tock, not tock-tick

5517 ab68 500
Reposted fromTriforce Triforce viaariso ariso
8740 ac92

This emergency exit sign.

Reposted frommyry myry viarunkenstein runkenstein

May 22 2017

1589 d259 500
Reposted fromlubisztosuko lubisztosuko viaaperture aperture

May 20 2017

I don't like this guy either, but fact is that he's wearing a walking cast for medical reasons.


So, in my art history class today, my professor was talking about something that is so fuckin awesome.


These are warrior shields from the Wahgi people of Papua New Guinea. The warriors paint them with imagery meant to symbolize animals who have traits they wish to embody in battle. These depictions are intended to give the person using it the powers of what they’re depicting.

Now. Look at this Wahgi shield:


Hmm. That looks a bit different from the others.


That looks VERY different. Why, it looks like


The Phantom… American comic book character by Lee Falk. And that’s because it is.


The Wahgi people were isolated from the rest of the “modern” world until 1933. They came into contact with WWII service men who shared some aspects of western culture with the tribesmen. In particular, they showed them the comic books they read while shipped out. The Wahgi loved them. In particular, the Wahgi adored the stories of the Phantom, who wasn’t even particularly popular in its home of America.

He is so popular that the few Wahgi who can read english will read the comics out loud in the village center and hold out the pages for everyone to see, so the whole tripe can enjoy them and marvel at the Phantom’s might in battle.

They identify with the Phantom because he came from a jungle territory, like them, wore a mask to fight, like them, and came from a long line of warriors, which the Wahgi, who worshiped their ancestors, deeply respected. Further, despite not really having superpowers, the Phantom is strong, clever, and incredibly fast. He was so fast that his enemies began to believe that he was impervious to bullets and could not be killed.

Therefore, the Wahgi began painting HIM on their shields to invoke HIS abilities in battle. There are TONS of Phantom-Wahgi shields out there.

So, you might think that you’re huge comic book fan, but the Wahgi have taken their Phantom fandom to the next level and have made the Phantom a fucking talisman to carry into battle for strength.

Reposted fromnerdtrap nerdtrap viaczinok czinok
Reposted fromFlau Flau viaaperture aperture

May 17 2017

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.

* 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 vianiklash niklash
9142 a69c 500
Reposted fromqb qb viaKryptonite Kryptonite
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!