Recently we’ve delivered a presentation to the Boston Azure User Group on how perfectly the cloud technologies are aligned for development for the Mobile Apps and clients. My coworkers from Blue Metal Architects delivered great content about integrating iOS (featured iPhone and iPad) and Windows Phone with the cloud. I’ve covered the use of the AppFabric Service Bus Queues and Topics – these technologies are perfect for communications for partially connected clients (like mobile ones).
Archive for the ‘Continuous Education’ Category
Posted by Igor Moochnick on 12/20/2011
Posted by Igor Moochnick on 11/29/2011
- MonoTouch – Create amazing iPhone and iPad apps with C# and .NET
- Reference Documentation for Timeline – SIMILE Widgets
- Five Absolutely Essential Utilities that make Windows better – Scott Hanselman
- Study Hacks »The Grandmaster in the Corner Office: What the Study of Chess Experts Teaches Us about Building a Remarkable Life
- It’s designed to improve performance. “The essence of deliberate practice is continually stretching an individual just beyond his or her current abilities. That may sound obvious, but most of us don’t do it in the activities we think of as practice.”
- It’s repeated a lot. “High repetition is the most important difference between deliberate practice of a task and performing the task for real, when it counts.”
- Feedback on results is continuously available. “You may think that your rehearsal of a job interview was flawless, but your opinion isn’t what counts.”
- It’s highly demanding mentally. “Deliberate practice is above all an effort of focus and concentration. That is what makes it ‘deliberate,’ as distinct from the mindless playing of scales or hitting of tennis balls that most people engage in.”
- It’s hard. “Doing things we know how to do well is enjoyable, and that’s exactly the opposite of what deliberate practice demands.”
- It requires (good) goals. “The best performers set goals that are not about the outcome but rather about the process of reaching the outcome.”
- Hard work is deliberate practice. It’s not fun while you’re doing it, but you don’t have to do too much of it in any one day (the elite players spent, on average, 3.5 hours per day engaged in deliberate practice, broken into two sessions). It also provides you measurable progress in a skill, which generates a strong sense of contentment and motivation. Therefore, although hard work is hard, it’s not draining and it can fit nicely into a relaxed and enjoyable day.
- Hard to do work, by contrast, is draining. It has you running around all day in a state of false busyness that leaves you, like the average players from the Berlin study, feeling tired and stressed. It also, as we just learned, has very little to do with real accomplishment.
The solution is as simple as it is startling: Do less. But do what you do with complete and hard focus. Then when you’re done be done, and go enjoy the rest of the day.
Posted by Igor Moochnick on 11/17/2011
- SignalIR Documentation
- WTF is a SuperColumn? An Intro to the Cassandra Data Model — Arin Sarkissia
- Sharding vs. Having multiple databases
- KnockoutJs: Introduction
- Ward Cunningham on Agile: 10 Years After
- Software Engineering Radio – the podcast for professional software develope
- How to do test reviews – a session at Øredev 2010
- Skills Matter : In The Brain of Greg Young: Simple is better
- User Interface Design Tutorial | Ryan Singer | PeepCode Screencast
- Copilot: a whole new product
- Aral Balkan | The Future is Native | Fronteers 2011 on Vimeo
- Peter Jackson’s The Hobbit, behind-the-scenes, 5k resolution, 48 fps, 3D
- THOUGHTS ON HOW KANBAN DIFFERS FROM SCRUM
- Synaptics shows conceptual trackpad interface with Windows 8, better make i
- Simple Hickey | 8th Light
- How Running A Business Changes The Way You Think
- A Field Guide to Developers
- Finding Great Developers – Joel on Software
- CommonJS Promises/A
- Deferred Object – jQuery API
- InfoQ: Better Best Practices
- Don’t Call Yourself A Programmer, And Other Career Advice | Kalzumeus Softw
- Why if you have implemented or in the process of implementing Scrum and are considering adding Kanban, you will want to evaluate that decision carefully
- Microsoft “Roslyn” CTP
- Hammock Driven Development
- InfoQ: Simple Made Easy
- New England Code Camp #16 – Eventbrite
- What You Don’t Know You Don’t Know (Hebrew) – Videos – Osherove
- Switched On: As Siri gets serious – Engadget
- Martin Fowler: Mocks Aren’t Stubs
- Dummy objects are passed around but never actually used. Usually they are just used to fill parameter lists.
- Fake objects actually have working implementations, but usually take some shortcut which makes them not suitable for production (an in memory database is a good example).
- Stubs provide canned answers to calls made during the test, usually not responding at all to anything outside what’s programmed in for the test. Stubs may also record information about calls, such as an email gateway stub that remembers the messages it ‘sent’, or maybe only how many messages it ‘sent’.
- Mocks are what we are talking about here: objects pre-programmed with expectations which form a specification of the calls they are expected to receive.