Very loose TypeScript might help in those cases, yeah. I tried very strict TypeScript in a project once and I probably spent more time trying to please the compiler and learning TypeScript than actually building stuff.
This tip to push through to the delivery goal is the best! We keep adding distractions and reasons to keep coding and ruminating the code, meanwhile we lose motivation due to lack of feedbacks.
Yeah.. kinda same there... after "refactoring" the thing million times i came to conclusion that i should invest into prototyping. Until prototype will not cover 80% of what i want to achieve, i will not invest a single minute into coding. Totally agree about distracting perfectionism. Same illness there... TypeScript, Git, linters, builders, what not... it's just eats up everything. The prototype will show the patterns and high level overview. And prototyping is fun. It's like gives you that satisfaction quickly.. the feel how it will work, clarity of architecture... etc, etc.
Cool video, very useful! I could use some dopamine kicks during the mundane parts of coding. I love writing/drawing the project our on paper, coming up with ideas, and coding the core of the project. But when it comes to polishing stuff, even finishing things up on the front-end, I get really bored and usually drop the project. It's mostly personal and practice stuff where there aren't any risks involved, so once I've figured the interesting parts out and solved the main problems, I don't feel like working on the easiest, remaining parts.
Same here. I'm working on identifying in advance the parts I'll find interesting and resisting the urge to do all those immediately, instead using them as longer-term motivators. I find I don't mind it, and when I'm done with a boring thing I don't feel demotivated because there are still exciting things ahead of me.
Hello MPJ, Could you please make a video about your environment setup, VS Code extensions and other tools that you're using? That would be super-interesting! Thanks
I don't really have one, I just use the plain editor. Reasoning in these videos: ua-cam.com/video/dIjKJjzRX_E/v-deo.html ua-cam.com/video/hlYiWznhhzw/v-deo.html
It sounds like in theory TDD is supposed to be the functional equivalent to what the sketching does for your project's form and vision. Then again I don't even code in my own development job, so what do I know? 😄
I don't want to conflate dopamine-reward & aiming for the nice feeling of having completed something, with doing a poor job when you know how to do better.
I've always found it incredibly annoying when I need to specify type and I'm not able to just use in Typescript. I spend just 10 minutes looking for the most abstract type that I can't find. At the end, it's so abstract what is even the point of including the type. I get it, very important in a serious project. But for side projects, why bother.
Bro i love your channel/content, but I have to say I disagree with avoiding TS/Unit Testing. What I DO agree with is being fast and dirty and working w/ the tools you know best. It's hard to avoid 'analysis paralysis' or getting caught in the rabbit hole of adding cool tooling to your project where it's not really needed. That dopamine rush of shipping a functional feature is what hooked me on development to begin with. Luckily with content creators like yourself, we can glom inspiration from articles, videos, repos, whatever and let that drive the future. Don't. Ever. Stop.
Lower my quality standard?
Say no more
Actually that is the hardest part for me ... developing a project with a quality lower than possible.
Use typescript, and just allow implicit anys, plain javascript is just brutal. You save a lot of time fixing/avoiding time consuming bugs.
Very loose TypeScript might help in those cases, yeah. I tried very strict TypeScript in a project once and I probably spent more time trying to please the compiler and learning TypeScript than actually building stuff.
Plain JS is just "Where is that error in my debug log coming from again?"
Maybe if you learn the fundamentals of JS you won't need to rely on a superset.
This tip to push through to the delivery goal is the best! We keep adding distractions and reasons to keep coding and ruminating the code, meanwhile we lose motivation due to lack of feedbacks.
Yeah.. kinda same there... after "refactoring" the thing million times i came to conclusion that i should invest into prototyping. Until prototype will not cover 80% of what i want to achieve, i will not invest a single minute into coding. Totally agree about distracting perfectionism. Same illness there... TypeScript, Git, linters, builders, what not... it's just eats up everything. The prototype will show the patterns and high level overview. And prototyping is fun. It's like gives you that satisfaction quickly.. the feel how it will work, clarity of architecture... etc, etc.
Cool video, very useful!
I could use some dopamine kicks during the mundane parts of coding. I love writing/drawing the project our on paper, coming up with ideas, and coding the core of the project. But when it comes to polishing stuff, even finishing things up on the front-end, I get really bored and usually drop the project. It's mostly personal and practice stuff where there aren't any risks involved, so once I've figured the interesting parts out and solved the main problems, I don't feel like working on the easiest, remaining parts.
Same here. I'm working on identifying in advance the parts I'll find interesting and resisting the urge to do all those immediately, instead using them as longer-term motivators. I find I don't mind it, and when I'm done with a boring thing I don't feel demotivated because there are still exciting things ahead of me.
Hello MPJ,
Could you please make a video about your environment setup, VS Code extensions and other tools that you're using?
That would be super-interesting! Thanks
I don't really have one, I just use the plain editor. Reasoning in these videos:
ua-cam.com/video/dIjKJjzRX_E/v-deo.html
ua-cam.com/video/hlYiWznhhzw/v-deo.html
It sounds like in theory TDD is supposed to be the functional equivalent to what the sketching does for your project's form and vision. Then again I don't even code in my own development job, so what do I know? 😄
I don't want to conflate dopamine-reward & aiming for the nice feeling of having completed something, with doing a poor job when you know how to do better.
The Circle CI link in the description does not appear to be correct
Thanks! Try now!
I've always found it incredibly annoying when I need to specify type and I'm not able to just use in Typescript. I spend just 10 minutes looking for the most abstract type that I can't find. At the end, it's so abstract what is even the point of including the type.
I get it, very important in a serious project.
But for side projects, why bother.
Hi MPJ...
Please make some videos about design patterns in javascript..
haha honestly, analysis paralysis is the almost the most enjoyable thing for me. Then again, I've never shipped anything, maybe that's why... :)
The journey greater than the destination.
Bro i love your channel/content, but I have to say I disagree with avoiding TS/Unit Testing.
What I DO agree with is being fast and dirty and working w/ the tools you know best. It's hard to avoid 'analysis paralysis' or getting caught in the rabbit hole of adding cool tooling to your project where it's not really needed.
That dopamine rush of shipping a functional feature is what hooked me on development to begin with. Luckily with content creators like yourself, we can glom inspiration from articles, videos, repos, whatever and let that drive the future.
Don't. Ever. Stop.
He didn't say to avoid it. Rather he recommends to postpone it until after you ship. I agree with him on this.
WHY NO USE SEMI COLONS AND DYE HAIR?????????????????????