Cowboy Coder: Difference between revisions
Jump to navigation
Jump to search
| [unchecked revision] | [unchecked revision] |
Content added Content deleted
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
Cowboy Coder doesn't waste time planning what he's going to work on or thinking through problems. Cowboy is ready to jump into writing code. Any problems we can fix when we get to them. |
Cowboy Coder doesn't waste time planning what he's going to work on or thinking through problems. Cowboy is ready to jump into writing code. Any problems we can fix when we get to them. |
||
Cowboy is very energetic. He reads a blog post and that inspires him to build [[GUI]]. He'll be hacking away at a C kernel but porting the [[C Library]] is difficult, so he decides to scrap his C kernel for assembly, twenty minutes into playing with GRUB, he believes he can do a better job [[Rolling Your Own Bootloader|rolling his own bootloader]], |
|||
Cowboy follows the [https://productcoalition.com/the-code-and-fix-model-2cabd4c48166 Code and Fix] software development method. |
Cowboy follows the [https://productcoalition.com/the-code-and-fix-model-2cabd4c48166 Code and Fix] software development method. |
||
| Line 30: | Line 28: | ||
==Opponents Position== |
==Opponents Position== |
||
Cowboy's |
Cowboy's opponents are [[Mister Perfect]] who overplans and it's never good enough, and [[Dae Dreamer]] who has never written a line of code. |
||
==People And OSes Related To Cowboy== |
==People And OSes Related To Cowboy== |
||
* [[User:Jankowalski25|Jankowalski25]] Definitely me. A lot of unfinished projects and test tools, but almost empty list of completed projects. Everything is flying and the question "what now?" always comes back. |
|||
* ''Insert your names here'' |
* ''Insert your names here'' |
||
Latest revision as of 15:20, 30 May 2022
Cowboy Coder doesn't waste time planning what he's going to work on or thinking through problems. Cowboy is ready to jump into writing code. Any problems we can fix when we get to them.
Cowboy follows the Code and Fix software development method.
Pros and Cons
Pros:
- He has a lot of passion.
- He doesn't waste time getting started.
- He will often follow a tutorial as a starting point but has no idea what to do once he reaches the end.
- He sees himself as a Jack of all trades.
Cons:
- Once the complexity of the task catches up to him, Cowboy doesn't have a plan, so he quickly looses motivation. As a result, Cowboy has many abandoned and unfinished projects. For example, he'll try to port a couple of C libraries to no avail, he'll try to roll his own, giving up not soon after, then deciding to restart over writing his kernel in Assembly or D.
- His motivation easily changes - one moment Cowboy will be working a bootloader, then read a blog post about UI design, and drop everything to work on a GUI.
- Trivial problems, when first encountered and not planned for, often prevent Cowboy from seeing the forest for the trees. For example, he'll focus his time on trying to avoid the next line of code from triple faulting, without caring to understand the bigger picture.
- Cowboy's questions on the forum are super-focused, with no context of the greater problem he's trying to solve, mainly because he doesn't know the greater problem himself.
Going further than Cowboy Coder
A vision of what you want your OS to be, and a TODO list to get there.
Cowboy's Bookshelf
Nothing. Reading takes time away from starting Cowboy's next project.
Opponents Position
Cowboy's opponents are Mister Perfect who overplans and it's never good enough, and Dae Dreamer who has never written a line of code.
People And OSes Related To Cowboy
- Jankowalski25 Definitely me. A lot of unfinished projects and test tools, but almost empty list of completed projects. Everything is flying and the question "what now?" always comes back.
- Insert your names here