- Aggregation in MongoDB Part I by Rick Copeland
- Aggregation in MongoDB Part II: Using MongoDB’s New Aggregation Framework in Python by Rick Copeland
- Fulltext Search with MongoDB and Solr by Derick Rethans
- Replica Sets Internals Bootcamp: Part III - Reconfiguring, by Kristina Chodorow
Nominations Open for the MongoDB Masters Program
Last year, 10gen launched the MongoDB Masters program, to encourage the exchange of knowledge and expertise amongst MongoDB community evangelists and open source contributors. After almost nine months working on the program, 10gen will be adding more MongoDB Masters to its roster for the 2013 Calendar year. What does it take to become a MongoDB Master? All of our masters have vastly distinct backgrounds, but two qualities make a MongoDB Master: A Commitment to Open Source MongoDB has a wealth of contributors from the open source community who support the growth of the MongoDB ecosystem. This includes development of MongoDB tools and patches and contribution to the free support forums. A Dedication to Evangelizing MongoDB These include bloggers, speakers, authors, MongoDB User Group (MUG) organizers and supporters who are dedicated to educating the community on MongoDB fundamentals and best practices. Our goal of this program remains the same: to honor the work of our community and foster the exchange of knowledge between and among 10gen and community leaders. MongoDB Masters have the opportunity to partake in the MongoDB Masters summit in Santa Clara, held before MongoSV in December, get two free tickets to the MongoDB Day of their choice and participate in workshops and online events with 10gen staff and fellow masters. 10gen is currently taking nominations for our second round of MongoDB Masters until June 15. If you would like to nominate a friend, colleague, or a user you follow on Github, please refer to the nomination page on the 10gen site. Tagged with: masters, experts, evangelism, developer evangelism, tech, startups, MongoDB, Mongo, NoSQL, Polyglot persistence, 10gen
The Rise of the Strategic Developer
The work of developers is sometimes seen as tactical in nature. In other words, developers are not often asked to produce strategy. Rather, they are expected to execute against strategy, manifesting digital experiences that are defined by the “business.” But that is changing. With the automation of many time-consuming tasks -- from database administration to coding itself -- developers are now able to spend more time on higher value work, like understanding market needs or identifying strategic problems to solve. And just as the value of their work increases, so too does the value of their opinions. As a result, many developers are evolving, from coders with their heads-down in the corporate trenches to highly strategic visionaries of the digital experiences that define brands. “I think the very definition of ‘developer’ is expanding,” says Stephen “Stennie” Steneker, an engineering manager on the Developer Relations team at MongoDB. “It’s not just programmers anymore. It’s anyone who builds something.” Stennie notes that the learning curve needed to build something is flattening. Fast. He points to an emerging category of low code tools like Zapier, which allows people to stitch web apps together without having to write scripts or set up APIs. “People with no formal software engineering experience can build complex automated workflows to solve business problems. That’s a strategic developer.” Many other traditional developer tasks are being automated as well. At MongoDB, for example, we pride ourselves on removing the most time-consuming, low-value work of database administration. And of course, services like GitHub Copilot are automating the act of coding itself. So what does this all mean for developers? A few things: First, move to higher ground. In describing one of the potential outcomes of GitHub Copilot, Microsoft CTO Kevin Scott said, ““It may very well be one of those things that makes programming itself more approachable.” When the barriers to entry for a particular line of work start falling, standing still is not an option. It’s time to up your strategic game by offering insight and suggestions on new digital experiences that advance the objectives of the business. Second, accept more responsibility. A strategic developer is someone who can conceive, articulate, and execute an idea. That also means you are accountable for the success or failure of that idea. And as Stennie reminded me, “There are more ways than ever before to measure the success of a developer’s work.” And third, never stop skilling. Developers with narrow or limited skill sets will never add strategic value, and they will always be vulnerable to replacement. Like software itself, developers need to constantly evolve and improve, expanding both hard and soft skills. How do you see the role of the developer evolving? Any advice for those that aspire to more strategic roles within their organizations? Reach out and let me know what you think at @MarkLovesTech .