wgroeneveld
/
brainbaking
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix categories link, thanks stue!

This commit is contained in:
Wouter Groeneveld 2022-10-10 20:57:21 +02:00
parent 675dcef73e
commit db5094e4ab
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/post/2022/10/why-are-software-engineers-engineers.md
View File

@ -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.

2
content/tags/_index.md
View File

@ -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 {`