Not All “Just JavaScript” is the Same
A developer uses a metaphor to explain how different JavaScript frameworks like React and Ember require varying levels of API knowledge.
A developer uses a metaphor to explain how different JavaScript frameworks like React and Ember require varying levels of API knowledge.
Argues that code reviews should be a team effort, not a single person's responsibility, to improve quality, share knowledge, and build ownership.
Explains Laravel 5.4's real-time facades feature, which allows creating facades on-the-fly without separate classes.
Explains why complex regexes are often wrong and unmaintainable, advocating for simpler, more robust validation methods.
A developer discusses the challenge of keeping up with rapid tech changes and shares a curated list of RSS feeds for staying current.
A developer shares his move to Berlin for a new Go role, his excitement for learning Go, and initial lessons from porting a Python project.
A recap of the first Python meetup in Lahore, discussing goals for PyCon Pakistan and community growth.
A philosophical look at JavaScript Fatigue, arguing software's purpose is solving business problems, not writing perfect code.
A tech lead's role is to guide the team's future direction, not just write code. Focus on strategy, planning, and empowering engineers.
A guide on how to approach and learn valuable lessons from legacy codebases, distinguishing between good and bad examples.
Explains how feature flags help development teams release features safely and control their visibility, using the django-waffle library as an example.
A programmer discusses techniques to reduce cognitive load when reading code, focusing on visual aspects like fonts, spacing, folding, and documentation.
A summary of the 2017 Paris sprint for scikit-learn, highlighting participants, achievements, and support for the open-source machine learning library.
Reflections on the benefits of constraints and collaboration at an R programming 'unconference', where participants built packages in two days.
A software engineer outlines seven common antipatterns for prioritizing feature requests in software development projects.
Final post in a Pythonic code series about leveraging PyPI packages to write better Python code by using community-developed tools.
A conference organizer reflects on launching ScriptConf, a JavaScript event in Linz, and helping organize the developer conference #devone.
A developer details their year-long process for creating and delivering a single, well-prepared conference talk, demystifying the work behind public speaking.
A product manager shares seven key habits of developers who consistently ship great, user-centric features, focusing on communication and ownership.
The Gnocchi project announces its decision to leave the OpenStack ecosystem to gain independence and improve development pace and contributor accessibility.