🏞 The Writing Process

{width=“598” height=“337” srcset=“tumblr_nk2ojojvBA1qz82meo1_1280.jpg 598w, tumblr_nk2ojojvBA1qz82meo1_1280-300x169.jpg 300w” sizes="(max-width: 598px) 100vw, 598px"} Nice illustration of the writing process, or any other creative/development endeavor, for that matter. Original Tweet: I love this illustration of this writing process. From Nicely Said book. pic.twitter.com/w5ccIVsrNX — ★ Sean Johnson (@seanuk) February 20, 2015 TODO: Link to the book source?

February 20, 2015 · 1 min · 53 words

📺 #noestimates

The problem? For example, 3 guys wrote a paper in 86 and they said that a good estimate is an estimate that’s within 25% of the original estimate, 75% of the time … so, mostly one quarter wrong . Yikes, not a very good prospect at all. The gist of #noestimates to determine how much scope can be delivered by a given date: Select the most important piece of work you need to do (highest value first) Break that piece of work down into risk-neutral chunks of work: (…) small enough that failing to deliver it at first attempt will not jeopardize the project [typically ~1 day chunks] Develop (…) Deliver that work to a production-like environment....

January 3, 2015 · 2 min · 238 words

🔗 Learn X in Y Minutes: Scenic Programming Language Tours

Learn X in Y Minutes: Scenic Programming Language Tours Learn X in Y minutes : Take a whirlwind tour of your next favorite language. Community-driven!

October 24, 2014 · 1 min · 25 words

🏞 (image)

The Flipboard Explorer, or FLEX, is a component that you can easily drop into any iOS project. When presented, FLEX shows a debugging toolbar that lives in a window above your app. From this toolbar, you can view and modify nearly every piece of state in the application. Unlike many other debugging tools, FLEX works entirely inside your app, so you donʼt need to be connected to LLDB/Xcode or a different remote debugging server....

September 30, 2014 · 1 min · 91 words

🔗 The Wilderness

The Wilderness It’s a period of time where I’m pretty lost, and I don’t know what to do. I have feature lists, I have open bugs to fix, and I have an outline of where the app is going. But I feel mentally incapacitated, like I’m getting nothing done. I call this “The Wilderness”.

September 30, 2014 · 1 min · 54 words

🏞 (image)

Not all technical debt is born the same, because A Mess is not a Technical Debt . (via TechnicalDebtQuadrant )

August 16, 2014 · 1 min · 20 words
Examples of a sketch, wireframe and mockup, side by side

💭 UI/UX design artefacts

Compare and contrast different design artefacts (sketch, wireframe, mockup, and prototype) in terms of their fidelity, speed, cost and use cases.

March 27, 2014 · 1 min · 134 words

🏞 (image)

(via What’s wrong with this picture? | Code.org ) Computer science is a top paying college degree and computer programming jobs are growing at 2x the national average . Less than 2.4% of college students graduate with a degree in computer science. And the numbers have dropped since last decade. See also Promote Computer Science | Code.org

March 27, 2014 · 1 min · 57 words

🔗 Richard Feynman, the Challenger Disaster, and Software Engineering : Gustavo Duarte

Richard Feynman, the Challenger Disaster, and Software Engineering : Gustavo Duarte With respect to software, I take out four main points: Engineering can only be as good as its relationship with management Big design up front is foolish Software has much in common with other engineering disciplines Reliable systems are built by rigorously tested , incremental bottom-up engineering with an ‘attitude of highest quality’

January 28, 2014 · 1 min · 64 words

🔗 Type-System Criteria · ongoing by Tim Bray

Type-System Criteria · ongoing by Tim Bray Cri­te­ria Let’s call them the Bánffy-Bray cri­te­ria for se­lect­ing be­tween sta­tic and dy­namic type sys­tems. Sta­tic typ­ing’s at­trac­tive­ness is a di­rect func­tion (and dy­namic typ­ing’s an in­verse func­tion) of API sur­face size. Dy­namic typ­ing’s at­trac­tive­ness is a di­rect func­tion (and sta­tic typ­ing’s an in­verse func­tion) of unit test­ing work­a­bil­ity.

January 24, 2014 · 1 min · 56 words