Information is different than knowledge, and part of the challenge of acquiring knowledge is being able to get back to information you know you've seen in the past if it seems relevant to something in front of you right now.
What eight years of side projects have taught me (2019)
71–80 of 91 posts
Re: What eight years of side projects have taught me (2019)
#72I like your blog's style and color. Do you have a blog dedicated to building it? Thanks
The short answer, though, is that I knew I wanted green in the color scheme (due to having grown up in the tropics), and I liked how James Hague did his blog https://prog21.dadgum.com/
The rest was just iterating on that.
Re: What eight years of side projects have taught me (2019)
#73I feel the same way.
However, I take it one step further. I lose interest after I create the one core feature that drew me to the project. I've made shoot em ups before, but I wanted to do one with enemies that flew in like Galaga. After I replicated the first few patterns, I lost interest. You couldn't even shoot the enemies, but I already knew how to do that.
Re: What eight years of side projects have taught me (2019)
#74For those who feel like a side project needs to be successful or reach a certain amount of revenue/lines of code/users to be successful in your eyes: Don't feel pressured. In my career (granted not a long one, but made it to C-Level in a startup after about 5-7 years) I've always used them to show my interest and learning skill to do something. It didn't matter whether it had 1 user or 1 million, employers were alway…
Re: What eight years of side projects have taught me (2019)
#75>The nice thing about the Go/Lua journal is that it’s far more flexible than the C# version, due to being able to write pages in Lua. Which means I’ll be able to To what?!?! D:
> Which means I’ll be able to use it for more things, and hopefully get that tight feedback loop back in place.
Re: What eight years of side projects have taught me (2019)
#76Earlier quoted context omitted.
In Haskell and Elm! Nice project. I did not see any code "shared" (or Elm generated from the Haskell code) to enforce type-safety across the network barrier. Afaik there are a few projects that could help with this. Not saying you need this (small project, easy to manage) but it's very sweet to have type safety from db, through BE app layer, though the wire format, all the way to the FE model code.
Close - Haskell & purescript!
Re: What eight years of side projects have taught me (2019)
#77Re: What eight years of side projects have taught me (2019)
#78Earlier quoted context omitted.
> The corporate world doesn't work like this. Everybody is paid a salary exchange for 45 hours of your life each week and your assignments are generally governed by an agile sprint cycle, so there is absolutely no motivation to be productive. I’ve consulted in a lot of large enterprises, and this is really untrue. If you’re happy just stagnating and some level that you’ve decided is good enough, you can get away with…
> But such people absolutely don’t develop their careers. Given the choice what is better: developing your career or your skills/competencies? Many developers learn some tool or giant framework instead of actually learning to write code or how to do their jobs because they are in a hurry to develop their careers. I would rather work with competent people who are less in a hurry to artificially justify their existence…
GP was saying that you only develop your career by developing skills. React is a skill, so is Angular, so is the wide world of front-end web programming.
Re: What eight years of side projects have taught me (2019)
#79For those who feel like a side project needs to be successful or reach a certain amount of revenue/lines of code/users to be successful in your eyes: Don't feel pressured. In my career (granted not a long one, but made it to C-Level in a startup after about 5-7 years) I've always used them to show my interest and learning skill to do something. It didn't matter whether it had 1 user or 1 million, employers were alway…
I get what you mean about not even really needing the project to work, just show that you have an idea and wanna work on it, yadda yadda, but I think you'll eliminate some good candidates and hard workers if you see a lack of side projects as a lack of devotion or work ethic.
Re: What eight years of side projects have taught me (2019)
#80For those who feel like a side project needs to be successful or reach a certain amount of revenue/lines of code/users to be successful in your eyes: Don't feel pressured. In my career (granted not a long one, but made it to C-Level in a startup after about 5-7 years) I've always used them to show my interest and learning skill to do something. It didn't matter whether it had 1 user or 1 million, employers were alway…
Hey, I know it's just a small comment on HN so I don't know the whole picture and you very well may already know/do this, but people who tend to have free time to just pump out side projects without worrying about work tend to be already-privileged people. I get what you mean about not even really needing the project to work, just show that you have an idea and wanna work on it, yadda yadda, but I think you'll elimin…