That's why I chose to reinvent the wheel a lot in the past. And sure, the code tends to take up less space,
and it is nice to be in control. But I've switched to reinventing wheels less often.
I make use of small extensions, that I can actually reach into and debug if I need to,
but i discourage that unless you plan on tweaking a library or you really enjoy tinkering with stuff.
I'm convinced that I have learned more by reinventing the wheel than I otherwise would have.
On a lower level, I mean. Because if I'd used libraries more often, for more tasks,
I would just have learned somthing else instead, on the larger picture.
It can also be very time consuming to reinvent the wheel,
and as many other things it's probably a matter of tradeoff and personal preferences.
I started out wanting to program games, but curious of nature,
I wanted to see and understand how "everything" works.
Then I'd naturally create as much as possible on my own,
and today I'd call myself a hobbyist engine developer. Not a game developer, yet.
But what do you feel like spending time on?
(Issues with space taken up by code is often an organization thing, IMO, don't worry too much about bloat; if there's good utility to a library then apply it.)
Show differencesHistory of post edits
#2SuperVGA
Posted 19 November 2012 - 10:56 AM
That's why I chose to reinvent the wheel a lot in the past. And sure, the code tends to take up less space,
and it is nice to be in control. But I've switched to reinventing wheels less often.
I make use of small extensions, that I can actially reach into and debug if I need to,
but i discourage that unless you plan on tweaking a library or you really enjoy tinkering with stuff.
I'm convinced that I have learned more by reinventing the wheel than I otherwise would have.
On a lower level, I mean. Because if I'd used libraries more often, for more tasks,
I would just have learned somthing else instead, on the larger picture.
It can also be very time consuming to reinvent the wheel,
and as many other things it's probably a matter of tradeoff and personal preferences.
I started out wanting to program games, but curious of nature,
I wanted to see and understand how "everything" works.
Then I'd naturally create as much as possible on my own,
and today I'd call myself a hobbyist engine developer. Not a game developer, yet.
But what do you feel like spending time on?
(Issues with space taken up by code is often an organization thing, IMO, don't worry too much about bloat; if there's good utility to a library then apply it.)
and it is nice to be in control. But I've switched to reinventing wheels less often.
I make use of small extensions, that I can actially reach into and debug if I need to,
but i discourage that unless you plan on tweaking a library or you really enjoy tinkering with stuff.
I'm convinced that I have learned more by reinventing the wheel than I otherwise would have.
On a lower level, I mean. Because if I'd used libraries more often, for more tasks,
I would just have learned somthing else instead, on the larger picture.
It can also be very time consuming to reinvent the wheel,
and as many other things it's probably a matter of tradeoff and personal preferences.
I started out wanting to program games, but curious of nature,
I wanted to see and understand how "everything" works.
Then I'd naturally create as much as possible on my own,
and today I'd call myself a hobbyist engine developer. Not a game developer, yet.
But what do you feel like spending time on?
(Issues with space taken up by code is often an organization thing, IMO, don't worry too much about bloat; if there's good utility to a library then apply it.)
#1SuperVGA
Posted 19 November 2012 - 10:52 AM
That's why I chose to reinvent the wheel a lot in the past. And sure, the code tends to take up less space,
and it is nice to be in control. But I've switched to reinventing wheels less often.
I make use of small extensions, that I can actially reach into and debug if I need to,
but i discourage that unless you plan on tweaking a library or you really enjoy tinkering with stuff.
I'm convinced that I have learned more by reinventing the wheel than I otherwise would have.
On a lower level, I mean. Because if I'd used libraries more often, for more tasks,
I would just have learned somthing else instead, on the larger picture.
It can also be very time consuming to reinvent the weel,
and as many other things it's probably a matter of tradeoff and personal preferences.
I started out wanting to program games, but curious of nature,
I wanted to see and understand how "everything" works.
Then I'd naturally create as much as possible on my own,
and today I'd call myself a hobbyist engine developer. Not a game developer, yet.
But what do you feel like spending time on? (Issues with space taken up by code is often an organization thing, IMO, don't worry too much about bloat; if there's good utility to a library then apply it.)
and it is nice to be in control. But I've switched to reinventing wheels less often.
I make use of small extensions, that I can actially reach into and debug if I need to,
but i discourage that unless you plan on tweaking a library or you really enjoy tinkering with stuff.
I'm convinced that I have learned more by reinventing the wheel than I otherwise would have.
On a lower level, I mean. Because if I'd used libraries more often, for more tasks,
I would just have learned somthing else instead, on the larger picture.
It can also be very time consuming to reinvent the weel,
and as many other things it's probably a matter of tradeoff and personal preferences.
I started out wanting to program games, but curious of nature,
I wanted to see and understand how "everything" works.
Then I'd naturally create as much as possible on my own,
and today I'd call myself a hobbyist engine developer. Not a game developer, yet.
But what do you feel like spending time on? (Issues with space taken up by code is often an organization thing, IMO, don't worry too much about bloat; if there's good utility to a library then apply it.)