layervault: I’m very excited to talk about a technique that we’ve started using at LayerVault. We call it Progressive Reduction. (…) How does one guide a new user from on-boarding, to low proficiency, to high proficiency? With progressive reduction, the UI adapts to the user’s proficiency. (…) Your proficiency in a product will decay over time without usage. As such, the proficiency reflected in the UI decays over time. Essentially, your UI regresses without usage....
we-are-star-stuff: If you’re interested in an IT degree and career, coding can be pretty intimidating. From understanding common programming languages to deciphering programming from developing, learning to code is necessary in today’s IT industry. The ability to implement a variety of programming languages can help you decide which coding career path is correct for you. Additionally, comprehending multiple popular programming languages will make you more marketable in the IT industry at large....
Willpower and cognitive processing draw from the same pool of resources. (…) Since both willpower/self-control and cognitive tasks drain the same tank, deplete it over here, pay the price over there. One pool. One pool of scarce, precious, easily-depleted resources. If you spend the day exercising self-control (angry customers, clueless co-workers), by the time you get home your cog resource tank is flashing E. (via Your app makes me fat — Serious Pony )
97 Things Every Programmer Should Know – Contributions Appearing in the Book Act with Prudence by Seb Rose Apply Functional Programming Principles by Edward Garson Ask “What Would the User Do?” (You Are not the User) by Giles Colborne Automate Your Coding Standard by Filip van Laenen Beauty Is in Simplicity by Jørn Ølmheim Before You Refactor by Rajith Attapattu Beware the Share by Udi Dahan The Boy Scout Rule by Uncle Bob Check Your Code First before Looking to Blame Others by Allan Kelly Choose Your Tools with Care by Giovanni Asproni Code in the Language of the Domain by Dan North Code Is Design by Ryan Brush Code Layout Matters by Steve Freeman Code Reviews by Mattias Karlsson Coding with Reason by Yechiel Kimchi A Comment on Comments by Cal Evans Comment Only What the Code Cannot Say by Kevlin Henney Continuous Learning by Clint Shank Convenience Is not an -ility by Gregor Hohpe Deploy Early and Often by Steve Berczuk Distinguish Business Exceptions from Technical by Dan Bergh Johnsson Do Lots of Deliberate Practice by Jon Jagger Domain-Specific Languages by Michael Hunger Don’t Be Afraid to Break Things by Mike Lewis Don’t Be Cute with Your Test Data by Rod Begbie Don’t Ignore that Error!...
People like us do stuff like this Seth’s Blog “There is no more powerful tribal marketing connection than this.”
What is the best horror story you can come up with in two sentences. : AskReddit I just saw my reflection blink. — marino1310 I begin tucking him into bed and he tells me, “Daddy check for monsters under my bed.” I look underneath for his amusement and see him, another him, under the bed, staring back at me quivering and whispering, “Daddy there’s somebody on my bed.” — justAnotherMuffledVo...
{width=“493” height=“559” srcset=“tumblr_mqf1c3xQG21r456j0o1_500.jpg 493w, tumblr_mqf1c3xQG21r456j0o1_500-265x300.jpg 265w” sizes="(max-width: 493px) 100vw, 493px"} HER DIARY: Tonight, I thought my husband was acting weird. We had made plans to meet at a nice restaurant for dinner. I was shopping with my friends all day long, so I thought he was upset at the fact that I was a bit late, but he made no comment on it. Conversation wasn’t flowing, so I suggested that we go somewhere quiet so we could talk....
Part 1: Why Microsoft’s reorganization is a bad idea Part 2: The uncanny valley of a functional organization Part 3: Services, Not Devices is the best way forward for Microsoft (via stratēchery by Ben Thompson )
Dan Shapiro » Shark Tank: The 3 worst startup mistakes made on TV’s best reality show Negotiate Here’s the simple rule. If someone makes you an offer, it’s because they’re interested. If they’re interested, you should negotiate. Not accept; negotiate. Know what you want (…) have a limited array of tricks up their sleeve, and you should have considered all of them before setting foot in that room. Stake size Controlling interest Number of Sharks investors A royalty Help Contingencies Don’t ever leave the room...
Dan Shapiro » How to read a patent in 60 seconds Step 1: Skip the title Step 2: Skip the drawings Step 3: Skip the abstract Step 4: Skip the specification Step 5: Find the independent claims, and read them Step 6: Back to skipping – toss the dependent claims [unless the independent ones are bogus/obvious] Useful for checking “requests for prior art” in Ask Patents