2 ms·
I think first of all, you need to understand what you want to get out of your project. It's okay to just explore a thing that seems cool, and if that is all tha
by marginalia_nu 5y ago
I think first of all, you need to understand what you want to get out of your project. It's okay to just explore a thing that seems cool, and if that is all that you want to get out of it, it's okay to abandon that exploration when you're full.
I've gone through a lot of hobbies and projects, and each and every one of them has left me more capable. This is fine. I've also embarked on bigger projects that have taken years.
If you are working for some particular goal, sometimes you need to push yourself a bit too. It isn't always glamorous, you won't always feel inspired; that stuff does wear thin as you get farther along. Sometimes it is a slog, and those days just showing up and going through the motions is plenty. Sometimes breaks can be good too, but they have a habit of becoming indefinite so it's dangerous territory.
> This translates to my work as well, (at a startup) where my title is, quite literally, "generalist." I do stuff ranging from the software side all the way to marketing, sales, and everything in between. It's working for now but I get the feeling it's not viable for the long run.
It is absolutely fine to be a generalist. Having insight into all these areas makes you extremely versatile, and allows you to look at problems in ways no specialist could. Especially at a startup, this is an amazing skillset.
- trms 5y agoFirst of all I love Marginalia, thanks for finishing _that_ project. :) Project scope seems to be key. I often get into things with 'lofty' goals but I should be more realistic about what I want to get from them. That requires a bit of thinking and self-reflection which, I think, I might be skipping. Acknowledging that not everything is glamorous is also another big part of it. When you just start something it's all new and shiny, but the bulk of the work is the unglamorous oiling of the gears and small improvements. I should internalize this fact. > It is absolutely fine to be a generalist. Thank you for stating that. It's rare (at least in my circles) to see generalists in startups so it's refreshing to see this.
- marginalia_nu 5y ago> First of all I love Marginalia, thanks for finishing _that_ project. :) > Project scope seems to be key. I often get into things with 'lofty' goals but I should be more realistic about what I want to get from them. That requires a bit of thinking and self-reflection which, I think, I might be skipping. Dunno, I think lofty goals are fine, but you need a clear idea why you want to accomplish them. Like if the reason you're learning some technology is because you want to learn it, and you find midway through that you don't want to learn it, then one of you must be wrong. Either you want to or you don't. It's fine to change your mind, you should be upfront about yourself about that. If it turns out you don't want to learn the thing, then you're wasting your time pushing yourself. It's also good to have some clue how to get there. When I built my search engine, I started by making a fairly simple prototype that consisted of a few components that each took a few weeks to get working. Having that made iterating on the design much easier. There's just no way I'd gotten where I am now if I didn't start where I did. > Acknowledging that not everything is glamorous is also another big part of it. When you just start something it's all new and shiny, but the bulk of the work is the unglamorous oiling of the gears and small improvements. I should internalize this fact. A lot of it may also be ensuring that you are doing the right things. I sometimes fall into the trap of just sort of tweaking things and not really making much of a difference. I've found it helpful to get some distance away from a project and to just think about it for a while instead of forcing myself to work directly at it every day. I often come back with a huge amount of ideas that I no doubt would have never come up with if I was closer to the project.