From db5094e4abca5fd57b3ecaccf9619fb8c36674a1 Mon Sep 17 00:00:00 2001 From: wgroeneveld Date: Mon, 10 Oct 2022 20:57:21 +0200 Subject: [PATCH] fix categories link, thanks stue! --- content/post/2022/10/why-are-software-engineers-engineers.md | 2 +- content/tags/_index.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/post/2022/10/why-are-software-engineers-engineers.md b/content/post/2022/10/why-are-software-engineers-engineers.md index 7198da96..f424ef18 100644 --- a/content/post/2022/10/why-are-software-engineers-engineers.md +++ b/content/post/2022/10/why-are-software-engineers-engineers.md @@ -20,7 +20,7 @@ In meeting rooms, when the engineer or architect has something to say, you bette For one, because the HR matrices tell us that engineers make more money than programmers. But why, what's the difference in their day to day job contents? -Many folks interpret the term "programmer" as a _bricolage_ person who just happens to put stuff together, press compile, and voila, it works! Programmers are viewed chaotic, have no moral compass and supposedly don't care about ethics or quality. They probably also don't know how to code and thrive in a team. Then you have your "developer", a sometimes seen as evolved version of the programmer who is able to read an API documentation and can perhaps "develop" their own. +Many folks interpret the term "programmer" as a _bricolage_ person who just happens to put stuff together, press compile, and voila, it works! Programmers are viewed as chaotic, have no moral compass and supposedly don't care about ethics or quality. They probably also don't know how to code and thrive in a team. Then you have your "developer", a sometimes seen as evolved version of the programmer who is able to read an API documentation and can perhaps "develop" their own. But what bigger companies _really_ want to hear (and see), is the **systematic appliance** of best practices, from design board to tests to deployment and long-term support. Both IEEE and ACM, two hugely influential computing learning societies, define software engineering as a systematic engineering approach to software development. Engineers---the real ones---are process experts. They design, divide into subsystems, make prototypes, evaluate outcomes, specify tests, and provide maintenance. diff --git a/content/tags/_index.md b/content/tags/_index.md index 284e8a87..9ad74f03 100644 --- a/content/tags/_index.md +++ b/content/tags/_index.md @@ -32,7 +32,7 @@ Not finding what you're looking for? Try browsing the archives: - [Retro](/categories/retro): Disassembling retro machines, cartridges, circuit boards, etc - [Education](/categories/education): Computing education, PhD work, findings in academica, etc - [Learning](/categories/learning): Self-improvement, meta-learning, reading and journaling, etc -- [Cooking](/cateogires/cooking): That home-kneaded egg pasta and smokey sourdough bread, etc +- [Cooking](/categories/cooking): That home-kneaded egg pasta and smokey sourdough bread, etc `} catch {`