"under the hood git rebase main is merging the current branch into main (it’s like git checkout main; git merge current_branch"
This is wrong. 'git rebase main' doesn't affect main at all! If you are on main and check out a new branch, then add commit-one, then switch back to main and add commit-two, then switch back to the new branch and 'git rebase main', your new branch will have commit-one and commit-two, and main will still only have commit-two.
it's much more like simply 'git merge main' with some extra magic to avoid a separate merge commit.
> I discovered that some were playing Q3 at ramped up physics speeds in single player. When going back to playing at regular speed, it feels like you're playing in slow motion.
That's amazing, like training at altitude but for e-sports.
it's not actually that helpful because a lot of the skill comes from muscle memory
and that's not just for aiming but mousemovement also has a significant influence on movement
for example there's something called a circle jump where you use precise mouse movement to get the most efficient angles so that your movement speed is maximized from your first jump
> just preparing for and attempting the interviews at [better companies]
This really rings true, I attempted and utterly failed an interview recently and was a real kick up the arse to improve myself - I'm no longer the hot shit I was 10 years ago.
We are a small, profitable company who build edible garden planning software. Our iOS app Garden Plan Pro was featured in a WWDC video, and we are now looking to rebuild our flash based planner in JavaScript. We're also working with the university of York on a research project to create a machine learning driven pest prediction service.
We are seeking to hire a new developer to help us deliver the next generation of garden planning software, and you'll be joining a small highly tech driven team and given autonomy and ownership over a brand new project.
I personally have been working here for 2.5 years and can attest to the fact that it is a really great company to work for, so feel free to chat informally to me (@user24 on twitter), or contact us directly via the website above!
On Tuesday the Guardian reported that the BBC (fondly aka Auntie) would be archiving their recipes, so I quickly scraped the site and wrote a search engine for it.
Not sure how the site will evolve, if at all, but it was a fun side project!
I thought archiving meant it would be no longer on their website, it would be awesome if they just released it all under something like the GPL. Could do some fun machine learning stuff with it...
I'd love them to release it as open data so that I'm not in murky waters.
If they move the recipes I can update the links. If they take the recipes down (which they've said they won't, now) I have got all the data so could rehost them.
edit: but, if you want to do some fun ML work, my scraper should help get you started!
This is wrong. 'git rebase main' doesn't affect main at all! If you are on main and check out a new branch, then add commit-one, then switch back to main and add commit-two, then switch back to the new branch and 'git rebase main', your new branch will have commit-one and commit-two, and main will still only have commit-two.
it's much more like simply 'git merge main' with some extra magic to avoid a separate merge commit.