|
|
The Difference Between Data Engineer and Data Scientist Roles in 2023
Join us as we traverse the fascinating world of data engineering and data science, exploring their unique attributes, collaborative aspects, and career opportunities. Discover how these professionals complement each other, weaving their skills together to create extraordinary machine learning solutions. Brace yourself for an illuminating journey that will equip you with the knowledge to navigate the evolving landscape of data-driven decision-making.
|
| DATA ENGINEER VS DATA SCIENTIST |
API-First Companies and What They Do Differently
You may have heard the term API-first, but what does it mean for organizations? In this article, we explain what API-first company is, the benefits of an API-first approach and how to get started.
|
| API-FIRST 101 |
|
[Webinar] Value of Personal Development Planning
|
17August at 11:00 AM EDT
In this webinar, we’ll discuss the value of designing, developing, and implementing a personal development plan. Individual development plans include approaches to better goal setting, improved focus, better time management, and improved relationships.
The webinar will provide frameworks for personal development plans that participants can tailor to their own needs while considering what might work best for them as they endeavor to improve.
|
| PERSONAL DEVELOPMENT |
|
|
|
[SE Radio Podcast] Software as an Engineering Discipline
Chad Michel, Senior Software Architect at Don’t Panic Labs and co-author of Lean Software Systems Engineering for Developers, joins host Jeff Doolittle for a conversation about treating software development as an engineering discipline.
They begin by discussing the need for engineering rigor in the software industry. Chad points out that many developers lack awareness of good engineering practice and are often unaware of resources such as the Software Engineering Body of Knowledge (SWEBOK). Among the many topics explored in this episode are design methodologies such as volatility-based decomposition and the work of David Parnas, as well as important topics such as quality, how to address complexity, designing for change, and
the role of the chief engineer.
|
| SOFTWARE AS A DISCIPLINE |
|
|
|
