1. What is DevOps (yet again)?
|
| Mike Loukides might define DevOps as the movement that doesn't want to be defined. Or the non-movement that’s resisting becoming a movement. Walking through a brief history of DevOps and different interpretations, he concludes that the goals of DevOps are much larger than facilitating the deployment and operation of web sites. What exactly is DevOps, then? |
2. John Allspaw on the culture of change
|
 "Rarely do we stop and attempt to understand why something went right, as opposed to something that went wrong."
—John Allspaw
This free, live training happens Wednesday, February 11 at 10am PT.
|
3. React in 7 Minutes
|
| Want a whirlwind out of Facebook's React framework? John Lindquist starts from scratch and builds an app in React in under 7 minutes, while teaching about building custom components, using React this.state vs. this.props, and React hooking up events. They said it was easy to learn. |
4. Downright personal
|
| The importance of personalization has hit home with retailers, many of whom have seen huge jumps in sales after beginning personalization efforts. Privacy concerns notwithstanding, consumers appear to be responding positively to everything from in-store beacons to personalized ads. Authenticity and trust seem to be the drivers. |
Sponsored Content
Monitor App Performance
|
 In-app analytics can only tell you so much about app performance. Keynote Mobile App Monitoring tracks the success and speed of app customer journeys on real smartphones and tablets in the cloud. |
5. Gender quota: is it the way?
|
| Is obligating companies to employ a certain number of women the right way to increase the number of women in IT? DevOps "Guy" JennyDevOps ponders thepros and cons of the matter. |
6. Don't care about mobile performance?
|
| Better think again. Tammy Everts shares some compelling evidence why you should care and presents it all in a nifty infographic. |
7. What goes into your stack?
|
When you consider how many tools and technologies are involved in the modern web stack, there are a lot of decisions to be made, writes Jason Yee, noting that there are so many that when O'Reilly's CTO, Andrew Odewahn, was exploring this space, his notes eventually grew to become The Field Guide to the Distributed Development Stack, an ongoing collaborative project.
Yee poses these questions: How have you selected the tools and technologies in your stack? And what considerations did you make with regard to containers and cloud hosting? Join the conversation here. |
8. First impressions count with mobile apps
|
| You've done it yourself: opened a mobile app, tapped, then closed it in disgust (and probably deleted it) because it failed to perform. Nikhil Kaul explains why testing is so crucial and offers a few pointers on what to test. |
9. Stress, strain, and reminders
|
| One question on John Allspaw's mind is "how do engineers (in their particular environment and familiarity with their tools) allow for them to adapt and learn?" No work in complex systems can be prescribed, Allspaw writes, which means it can’t be codified, and it can’t be proceduralized. Instead, rules and procedures and code are the scaffolding upon which operators, designers, engineers adapt, in order to be successful. |
댓글 없음:
댓글 쓰기