Duct von Tape: Difference between revisions
| [unchecked revision] | [unchecked revision] |
No edit summary |
|||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
Duct likes mixing code from beginner tutorials, half-way projects and completed projects. He doesn't stick to one coding style, one naming convention, etc. He doesn't have specific goals that he can achieve by understanding what is he doing, because simply he doesn't understand what is he doing. Anyway his project will be used [[Beginner Mistakes#Assuming It Will Go Nowhere|only by himself]]. |
Duct likes mixing code from beginner tutorials, half-way projects and completed projects. He doesn't stick to one coding style, one naming convention, etc. He doesn't have specific goals that he can achieve by understanding what is he doing, because simply he doesn't understand what is he doing. Anyway his project will be used [[Beginner Mistakes#Assuming It Will Go Nowhere|only by himself]]. |
||
== |
==Pros and Cons== |
||
Duct's approach has one pro: he can make use of the open-source nature of many projects. On the other side, con's are much more: |
Duct's approach has one pro: he can make use of the open-source nature of many projects. On the other side, con's are much more: |
||
| Line 7: | Line 7: | ||
* He creates many bugs while he is unable to fix any of them |
* He creates many bugs while he is unable to fix any of them |
||
* He makes his code totally unreadable to others and to himself |
* He makes his code totally unreadable to others and to himself |
||
* He doesn't learn much from it |
|||
==Duct's Bookshelf== |
==Duct's Bookshelf== |
||
| Line 21: | Line 22: | ||
[[Category:Developer Archetype]] |
[[Category:Developer Archetype]] |
||
[[Category: |
[[Category:Developer Anti-Pattern]] |
||
Latest revision as of 12:39, 18 June 2020
Duct likes mixing code from beginner tutorials, half-way projects and completed projects. He doesn't stick to one coding style, one naming convention, etc. He doesn't have specific goals that he can achieve by understanding what is he doing, because simply he doesn't understand what is he doing. Anyway his project will be used only by himself.
Pros and Cons
Duct's approach has one pro: he can make use of the open-source nature of many projects. On the other side, con's are much more:
- He mixes incompatible licenses
- He creates many bugs while he is unable to fix any of them
- He makes his code totally unreadable to others and to himself
- He doesn't learn much from it
Duct's Bookshelf
None really, every snippet of code, even when irrelevant, can be integrated to his project.
Opponents Position
Writing an OS is a hard task that can't be achieved by copying and pasting random snippets of code. One has to know what does he do and how everything works together. In short, Duct is not the appropriate archetype for an OS developer.
People And OSes Related To Duct
- Insert your names here