Informationweek Influencer
(•_•) ( •_•) (⌐■_■) (@moonpolysoft)
- Twitter Bio:
- T-Rex arms with retard strength.
- Location:
- 8========D~~~
- Website:
- http://i.imgur.com/bmACi.gif
(•_•) ( •_•) (⌐■_■)'s Selections From the Web
I’ve been thinking about the lessons distributed systems engineers learn on the job. A great deal of our instruction is through scars made by mistakes made in production traffic. These scars are useful reminders, sure, but it’d be better to have more engineers with the full count of their fingers.New systems engineers will find the Fallacies of Distributed Computing and the CAP theorem as part of their self-education. But these are abstract pieces without the direct, actionable advice the inexperienced engineer needs to start moving[1]. It’s surprising how little context new engineers are given when they start out.Below is a list of some lessons
Upcoming Events
Live Events
- BYOD into the Cloud: The Next Phase of Enterprise Mobility -
- Digital Disruption - E2 Conference Boston
- The Language of UX: Beyond Buzzwords -
- Get practical strategies to build a solid plan for profitability and success - Mobile Commerce World - Mobile Commerce World
- The E2 Social Business Leaders - E2 Conference Boston - E2 Conference Boston
This Week's Issue
Free Print Subscription
SubscribeSpecial Issue
Current Government Issue
In this issue:
Subscribe Now
- The Government CIO 25: These influential and accomplished government IT leaders are finding ways to be cost efficient and still innovate.
- Rethink Video Surveillance: It's not just about networked cameras anymore. New technology provides analytics, automation, facial recognition, real-time alerts and situational-awareness capabilities.
- Read the Current Issue












