Skip to content

Commit

Permalink
fucked up rebase, fixed it now (#10)
Browse files Browse the repository at this point in the history
  • Loading branch information
@youshy
youshy authored Jan 4, 2022
1 parent d67bc7d commit c484dd8
Showing 1 changed file with 60 additions and 0 deletions.
60 changes: 60 additions & 0 deletions content/posts/2022-01-05-Love-The-Job-You-Hate.md
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,60 @@
---
date: "2022-01-05T00:00:00Z"
title: Love The Job You Hate
draft: false
toc: true
tags: [hobby, jobs]
---

New year, new me ey?
I want to give you another angle on *ditch your job and follow your dreams* idea.
And this is coming from a guy who used to do my passion for a living and have reworked my idea about it.

> If you need a soundtrack for this post, I really recommend [Honne](https://www.youtube.com/watch?v=2dSBarxs3F8).
## Keep Your Expectations In Check

I'll go right out of the gate and drop the truthbombs now - if your side-hussle is not a full time gig and/or you're not 100% honest with yourself - the mean rate of return from your hobby might not be the greatest.
You can get a lot from your after-work gig, but it requires time. The more you put in, the more you get out - it's basically like investing in stock market, you can't get a million from $1 investment.

Well, you can, but it requires a lot of time and even more luck.

## Not Every Hobby Has To Be A Hussle

And this is where we get into the actual topic of this post - **not every hobby has to be a hussle**.
We're living in a world, in which, everywhere you go, you see an influencer, telling you how well they're doing living off their passion.
Everything is covered in hyperachiever-sauce with a hint of desperation.
You shouldn't feel pushed to make your knitting hobby into a full-time Etsy shop, or your after-work small code sessions into a career.
The reason is simple - when you do cross the line and turn your hobby into work, the things change - suddenly, you have to manage an inventory or deal with customers or have a Sprint retrospective every week - and then you end up hating the job you've thought you'll love.

## Love The Job You Hate

Most of us used to be in a place, where you've stared a new interest in something and then thought about making it a full time thing.
The problem with this is that when the adrenaline and the dopamine kicks in, you get a massive tunnel vision - only the way you think about the goal is right and there's no other way of getting to the finish line.
When all of that starts to pick up the slack, there's an overwhelming feeling of dread and annoyance with your current job.
You're starting to feel like it's restricting you and not allowing you to really fly and do what you love.

Although the title of this paragraph might be a tad misleading/triggering for some, what I want to convey is that you need to **give yourself some time**.
If you're in a dead-end/really bad job, most of the time, it's actually better to quit right out of the gate (and welcome to this post's multiverse!) and either grab another part-time gig or YOLO it and just go with the newfound passion.
But if you're in a somewhat stable, warm and cosy gig, embrace it for a while.
Take it from me, before, I've used to live from my passion, used to work 18hrs a day, balancing finishing uni, teaching full time and working full time.
Now, I've found the path for me and I know how to get where I want to get.
But it took me, literally, years to get to this point.

## It's OK To Pivot

Okay, let's say, right now, you're knee deep in your journey, you know the angles, but then, the inevitable comes and you're starting to feel like that's not the thing.
Maybe you've spent a month or a year on this hobby, but the next thing feels like it might actually be the one.
What you should do then?

Well, do the same thing as the one when you've started the previous thing - explore.
Once you'll get a little deeper into the rabbit hole, you shouldn't be afraid to pivot and change direction - always remember, that the things you've learned so far, allows for a better foundation of the next thing.

## Follow Your Gut

All of that above can be dismissed with just a right feeling and the perfect combination of perseverance and luck.
If you feel like you're ready to follow your passion, that it's the greatest thing in the world, it feels right AND you'll be able to survive before you'll get to the top - **do it!**
The older I get, the more I go with not even *doing things safe* but *doing things smart* - I want the things that I do to bring some value, I want to be proud of them and I really don't want to restrict my growth in other avenues of my life.
I did both ways (doing the bare minimum and YOLO) and I've found doing things smart to have the golden ratio between these ways.

Now it's your turn to figure it out!

1 comment on commit c484dd8

@github-actions
Copy link

@github-actions github-actions bot commented on c484dd8 Jan 4, 2022 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@check-spelling-bot Report

Unrecognized words, please review:

  • Etsy
  • Honne
  • hussle
  • hyperachiever
  • SBarxs
  • truthbombs
Previously acknowledged words that are now absent cdn cej dtp eep eepurl FTM Miasto Nocny Powiedz
To accept these unrecognized words as correct (and remove the previously acknowledged and now absent words), run the following commands

... in a clone of the [email protected]:youshy/blog.git repository
on the main branch:

update_files() {
perl -e '
my @expect_files=qw('".github/actions/spelling/expect.txt"');
@ARGV=@expect_files;
my @stale=qw('"$patch_remove"');
my $re=join "|", @stale;
my $suffix=".".time();
my $previous="";
sub maybe_unlink { unlink($_[0]) if $_[0]; }
while (<>) {
if ($ARGV ne $old_argv) { maybe_unlink($previous); $previous="$ARGV$suffix"; rename($ARGV, $previous); open(ARGV_OUT, ">$ARGV"); select(ARGV_OUT); $old_argv = $ARGV; }
next if /^(?:$re)(?:(?:\r|\n)*$| .*)/; print;
}; maybe_unlink($previous);'
perl -e '
my $new_expect_file=".github/actions/spelling/expect.txt";
use File::Path qw(make_path);
use File::Basename qw(dirname);
make_path (dirname($new_expect_file));
open FILE, q{<}, $new_expect_file; chomp(my @words = <FILE>); close FILE;
my @add=qw('"$patch_add"');
my %items; @items{@words} = @words x (1); @items{@add} = @add x (1);
@words = sort {lc($a)."-".$a cmp lc($b)."-".$b} keys %items;
open FILE, q{>}, $new_expect_file; for my $word (@words) { print FILE "$word\n" if $word =~ /\w/; };
close FILE;
system("git", "add", $new_expect_file);
'
}

comment_json=$(mktemp)
curl -L -s -S \
  --header "Content-Type: application/json" \
  "https://api.github.com/repos/youshy/blog/comments/62899897" > "$comment_json"
comment_body=$(mktemp)
jq -r .body < "$comment_json" > $comment_body
rm $comment_json

patch_remove=$(perl -ne 'next unless s{^</summary>(.*)</details>$}{$1}; print' < "$comment_body")
  

patch_add=$(perl -e '$/=undef;
$_=<>;
s{<details>.*}{}s;
s{^#.*}{};
s{\n##.*}{};
s{(?:^|\n)\s*\*}{}g;
s{\s+}{ }g;
print' < "$comment_body")
  
update_files
rm $comment_body
git add -u
If you see a bunch of garbage

If it relates to a ...

well-formed pattern

See if there's a pattern that would match it.

If not, try writing one and adding it to the patterns.txt file.

Patterns are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your lines.

Note that patterns can't match multiline strings.

binary-ish string

Please add a file path to the excludes.txt file instead of just accepting the garbage.

File paths are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your files.

^ refers to the file's path from the root of the repository, so ^README\.md$ would exclude README.md (on whichever branch you're using).

Please sign in to comment.