You're raising a great point. While I'm not living together with my partner, we do have a little family and I'm very much with you that it's super hard to get anything done with kids around.
Unless you get up super early, stay up super late after kids are in bed, or use the time when they aren't around (e.g. kindergarden), I also think that it's almost impossible to fully focus on something for a longer period.
I guess it kind of boils down to finding the right routines. That certainly doesn't make it easier...
Sorry for the late reply, I didn't realize people were actually commenting here...
So coming back to your question:
In my case, I'm lucky enough to work for a company that is entirely distributed and decentralized and doesn't actually tell me when and how long to work as long as the output is sound.
Obviously, in practice you most often have to put in some hours to get stuff done (that's what I'm being paid for after all). So while my work schedule isn't enforced, I chose for myself to work at these hours (not just for my employer) because I tend to function best at those hours.
Now... do I want to reserve several hours of each day for work for the rest of my life? Certainly not. But that's what work right now for me and it can and will totally change in the future.
I'm documenting my journey of learning the Rust programming language with blog posts that are easy to understand (hopefully), especially for people without a systems programming background (like me).
I'm accumulated a bunch of articles already an decided to create an every growing twitter thread where people can follow my journey and learn alongside with me.
Hopefully this is useful for some people out there.
I made it a challenge for myself to author and publish an ebook about Git in two months. This has worked out wonderfully and now I'd like to share my process, workflow, learnings and key takeaways.
I hope there's some useful tips for potential authors here!
I'm probably not very good at expressing that the book is not only about rebasing. While it is the main focus, the book covers a lot of other things that aim to give you a really good understanding of the tool (which I believe is necessary to make sense of (interactive) rebasing).
And just like you said, you can totally get around with adding/committing/pushing changes without ever touching the rebase command. Perfectly fine.
If you want to be more flexible and productive with your work, you might want to learn how to rebase though.
Just to clarify this: The aim of rebasing is not a clean commit history. It enables you to make one in case you've been creating lots of work-in-progress commits with no semantic meaning, which makes it harder to work with it.
However, even if you stick to that, it's not like rebasing isn't of value anymore. You might still be interesting in squashing your commits or splitting them up or simply rebase on branch on top of another for various reason.
That said, I'd recommend to not advocate not to rebase if it's based on the assumption that it's only useful for clean commit histories.
I understand this reaction. And just like you've pointed out, it's actually not a whole" book about a single command.
In order to get a good understanding of rebasing, I believe it's good to have a solid foundation of how git works, which is pretty much what the first half of the book covers.
I could've left that out and only talk about rebasing without going into all the other topics but then, for someone who isn't experienced with the internals of git will have a hard time following what's going on.
`git add i` is indeed powerful and lets you interactively craft your index before you create a commit. It doesn't enable you to split up an existing commit though.
If there's one tool I'd recommend everyone to learn it's rebasing. Especially interactive rebasing because it enables things like splitting commits apart, squashing them together and even run automated programs.
over the past two months I made it myself a challenge to write an ebook about rebasing in git and today I'm happy to launch a first version of it!
I see a lot of people struggling with having a fundamental understanding of how git works. Rebasing in Git is probably one of the most powerful features of the tool that can make everyone extremely productive when it comes to version control and working with peers on projects.
I just took a look at your course platform and it looks really interesting! I like the interactive editor and also the fact that it comes with an integrated test runner. Well done!
You might want to look into how to make landing pages a bit more attractive though as it's not selling your platform "strongly" enough.
That's correct! You'll be able to execute your machine learning code in our cloud + plus you can share it with others for easy exploration.
For uploading data sets we're working on a resolver strategy that lets you specify endpoints from where the data can be downloaded before the lab is executed.
We'll provide containers with all common libraries. In the future you'll be able to configure your own containers which will allow you to run pretty much whatever you want.
You're raising a great point. While I'm not living together with my partner, we do have a little family and I'm very much with you that it's super hard to get anything done with kids around.
Unless you get up super early, stay up super late after kids are in bed, or use the time when they aren't around (e.g. kindergarden), I also think that it's almost impossible to fully focus on something for a longer period.
I guess it kind of boils down to finding the right routines. That certainly doesn't make it easier...