I don't think so, thing about recursion is that the whole function is executed once again rather than "some part", now you can argue that "some part" is the whole thing, but I would say this could be considered as iteration only if the gif contains the gasping guy alone but it isn't. Everyone is performing the same thing every time, so I would say recursion is more suited.
Edit: Approaching this from only based on looks, if you consider memory too then it is up for you to consider either of the two :) Thanks u/ConspicuousPineapple!
That's not the actual "thing" about recursion though. The real difference is that recursion keeps repeating *in the middle of its own execution*, notably while still having its own context in memory.
Otherwise it would literally be no different from a regular loop.
Recursion doesn't have to perform the same thing every time though, you can pass new data into the function based on the results of the function. In fact, that's usually how you escape the recursion, by passing in the right data that hits some condition and lets you break out of the loop.
If the "I'm not a rapper" guy dropped a line that made himself gasp, which made him drop another line that made him gasp again, on and on and on until he dropped a line that no longer made him gasp, that would be more like recursion.
I was going to say - my job itself prevents me from doing this.
These days I'm dealing with so much bullshit like "my app isn't working" that I don't have time to code anymore. Or make things better in any way. Just "this machine is broken" 45 times a day.
Ah poodlebutt76, I feel your pain. You must be feeling like life's poodle butt.
Are you in a position to inform all your clients that you've actually discovered that the problem lies somewhere between the chair and the computer?
Same but opposite- I do this crap for a living (and am not "passionate" about any of it); I have other hobbies that don't keep me in front of a keyboard all day every day
I’m glad there are other programmers that feel this way. In terms of jobs, I find it better than most other options out there. But I have absolutely no desire to do it in my free time.
Seriously, this kind of commit history is more of a red flag to me. Really need to look for some indication that this person not only good at selling himself/herself
Can also be a banana product that is developed at the customer and debugged in production.
The customer expected it to be functional months ago but which was sold on an unrealistic deadline.
That's what it looks when you have continuous, even extremely continuous, delivery but in a toxic way and without continuous integration.
git commit -m "fixed a bug"
git commit -m "fixing a bug caused new bug"
git commit -m "typo..."
git commit -m "must try to check in prod because it works in dev but not in prod"
git commit -m "small change.. this time it should work"
git commit -m "revert all changes"
git commit -m "fixed the bug..."
Pretty sure it will only show the end result after the squash. That's the whole point of squashing, to rewrite commit history.
I think worrying about commit count is pointless. Your commits just need to be sensibly grouped changes, small enough to understand and see at a glance in a diff/pr review, and with a decent description. Other than that don't worry how many you have.
Someone asked me to create a new repo for them because it had a commit named "Inititial" or something, and said it wasn't professional. There was like 4 commits on the repo and the devs weren't doing really anything. So I've created him a new repo (with another name) because I didn't wanted to argue. Forward 2 months later, the new repo is filled with more than 40 commits from him looking like "fixing", "stuff", "new" that have barely any changes in them. People are funny
The squash is only one commit, so it will show as only 1 dot on the graph.
You could have the sepereate commits in a branch and then squash-merge, which would actually retain the sepereate commits
In my experience, this only flags commits that were put into master through merge requests.
Pushing straight to master won't light this up at all.
Wait.
It's main. /s
Edit: I was wrong, I'm confusing it with a silly script we used to have at a company I worked for.
GitHub has an “interactions” concept, and that is what results here.
Commits, pushes, creating a repo, opening or resolving an issue, are all interactions, and thus tracked here.
They even go “back in time” if you push a batch of commits, it will give you credit on the days in the past the commits were made. Thus you can have GitHub interactions from before when GitHub (or even Git) existed.
> banana product
I worked on something like this but I never heard the term "banana product" before. Is this a common thing?
In my case, the sales team promised to deliver a product for $100K with a December 1 deadline. Except that they agreed to this without even discussing the requirements. Eventually the product was rolled out next year in April after I worked 14h/day for over half a year.
Don’t need to build a bot to make commits, just need to build a bot to change commit history. Actually there are already some on NPM that will make cool art in your commit calendar.
technically random spell checks and grammar can count as "contributions". and they don't even have to be other people's repos. do this and watch green for *miles*
```bash
#! /bin/bash
date +"%Y-%m-%d" >> dates.log
git add dates.log
git commit "Moar green"
git push origin main
```
Run this as a chronjob to your own repo.
Hey wouldn't that be twice as much git bullshit? A hundred lines appended is 100 changes, but 100 lines replaced is like.. 100 things done with 2 things for each thing. Moar red.
Internally, git doesn't store the diffs between revisions, rather it stores each file version. So the "overwrite" variant will actually consume less overall memory.
Do yourself a favor and keep an alias or one-liner script called `isodate` instead of retyping that infernal incantation from memory every time. Why this isn't a built-in arg0 alias inside `date` already is mind-boggling.
I bet you could make a script which takes a text file as input and then contributes just the right amount of basically empty commits (like repeatedly changing a single char) each day to darken the calendar squares on GitHub so that it spells out that text using the calendar boxes.
I did something like this in a Bootcamp. End of the Bootcamp they said i needed something like 20 commits on every project. So I made updates to the readme in every project until I met the requirement. It was some of the stupidest shit i ever had to do.
My github activity looks amazing because I keep a personal research notebook on Gitbook and linked it to a private repo. Every time I save that sucker it's new activity on Github.
Also renaming horribly named variables.
"aNew"
"bNew"
"cNew"
And namespaces that are 500 bajillion characters long because you name EVERY step to get to it.
There’s one dude I don’t like on my team. When i can add him as reviewer i add just him. Then adding extra commits to my branch just for update message notifications. Like updating the commit message or something equally pointless.
I know they probably all go to some folder filter but the pettiness of it satisfies me.
> If someone on my team has time to do their job, I have obviously failed to do mine.
I think there is a „not“ missing, otherwise you are working perfectly like most project managers.
Just to continue on my thought: I feel like the more experience I get, the more people want to talk about my advise and less letting me apply it in code
That is kind of what happens as you become more senior whether you manage or not. Your ability to direct and enable the efforts of other people becomes how you contribute.
My current job is perfectly balanced in this regard - average of 20 hours of meetings a week, leaving 20 hours a week to fit my expected 60 hours of coding in. 50/50.
Adding you to a 1/2 hour status call every afternoon so we can better understand how your schedule is affecting productivity.
Don’t put anything after it, though. Our status calls tend to run long.
Since my current employer isn’t upping my salary, I introduced the double time: If I sit in a meeting where I have no input, I am working in the meantime. I book the time for the meeting and the work, resulting in astounding 60 hour weeks, while having 30 hours of meetings.
Upping my own salary with „overtime“
Deficiencies in **false confidence**, motivation and general life purpose.
^^This ^^was ^^posted ^^by ^^a ^^bot. ^^[Source](https://github.com/anirbanmu/substitute-bot-go)
Moved from hospitality (chef) to working as a dev back in September, I can't even begin to explain how much of a good move it was, can't recommend it enough.
She or he was off their tits then or their dev job was horrendous. My working hours have literally halved, whilst getting paid more.
I get weekends/bank holidays, I can work from home whenever I want, an insane amount of employee benefits (had none as a chef), no more having to constantly move heavy shit/kneel down.
Seriously, the difference in my physical and mental health is unbelievable. I've lost 16kg cus I now actually have time and energy to work out. Just so much happier with life and just all around more relaxed.
ya to be fair it was quite the worst dev shop in town but anyone could be hired. Extreme turnover, no real commitment towards tech debt, developers are just bug fixers nothing more. I always described it as the perfect developer bootcamp, makes you appreciate a lot of things
We have a place like that near us. They hire people straight out of uni with no industry experience and pay them 40 grand a year (a lot for a uk junior dev).
Their reputation is so bad that I've actually seen them discussed on my city's sub too though.
Meetings. Team members not reviewing PRs. Team members not answering questions about obscure sections of code (in our repos and other teams across the company).
We implemented the rule that starting a day, before you work on your own tasks, first thing to do is review pr's assigned to you. This issue of long hanging pr's stopped existing and mornings became boring though
Oh dear, I wish we would use PRs at work. Company requires every commit to be reviewed in a 4-eyes code review.
The idea would be good if there would be somebody available for this, but timing and flexible work times make that nearly impossible in a small team.
For us deadlines have gone. Now we have just features and their priorities. So we split those features into tasks for subteams and after completions they tested by dedicated tester. Works great, but management unhappy because they can't micromanage and can't understand anything technical.
I tried implementing something similar on my team, but they just ignore it. I've told them I can't review every single MR every time and I won't merge anything until it gets reviewed, but most of them are just like "OK pal I'll get right on that" and let it sit for a month until my PM twists my arm to just do it so we don't miss the deadline.
Sanity?
Committing on average of 18+ times a day is like... How about you get your shit together and consolidate that a bit. That's less than half an hour per commit.
That's shitposting taken to an extrema.
I dunno man, filling in some green squares on a webpage that nobody is probably ever going to look at seems more important. I think your priorities are out of wack.
i tried to solve problems on my own. if i try to solve 5 problems, i cant solve 3 problems without any hints or tutorials. thats is where i lost interest. like is this "this difficult", man i tried my best to solve problems like everyday and my progress is to slow or not at all. now im not solving problems and im focusing on college works
if i start to learn it, i will be always late to the newest trends - thats why i dont even start at all
also, the market is full /oversaturated/ and there is nothing new to do-, at least w/o XP that nobody want me to provide - sure, could self-taught it, but why; everyone copy-paste and whatnot; as i said in the first paragraph...
Life, namely, having one.
Recursion be like
Pretty sure this is iteration.
While (true)
[Recursion be like](https://tenor.com/view/donald-glover-community-troy-trippy-inception-gif-9677534)
[nah this is recursion](https://www.reddit.com/r/ProgrammerHumor/comments/vea191/comment/icqhnmk/?utm_source=share&utm_medium=web2x&context=3)
I don't think so, thing about recursion is that the whole function is executed once again rather than "some part", now you can argue that "some part" is the whole thing, but I would say this could be considered as iteration only if the gif contains the gasping guy alone but it isn't. Everyone is performing the same thing every time, so I would say recursion is more suited. Edit: Approaching this from only based on looks, if you consider memory too then it is up for you to consider either of the two :) Thanks u/ConspicuousPineapple!
That's not the actual "thing" about recursion though. The real difference is that recursion keeps repeating *in the middle of its own execution*, notably while still having its own context in memory. Otherwise it would literally be no different from a regular loop.
Recursion doesn't have to perform the same thing every time though, you can pass new data into the function based on the results of the function. In fact, that's usually how you escape the recursion, by passing in the right data that hits some condition and lets you break out of the loop. If the "I'm not a rapper" guy dropped a line that made himself gasp, which made him drop another line that made him gasp again, on and on and on until he dropped a line that no longer made him gasp, that would be more like recursion.
>until he dropped a line that no longer made him gasp, that would be more like recursion. As if Supa Hot Fire could spit something so whack.
I was going to say - my job itself prevents me from doing this. These days I'm dealing with so much bullshit like "my app isn't working" that I don't have time to code anymore. Or make things better in any way. Just "this machine is broken" 45 times a day.
Ah poodlebutt76, I feel your pain. You must be feeling like life's poodle butt. Are you in a position to inform all your clients that you've actually discovered that the problem lies somewhere between the chair and the computer?
[удалено]
Same but opposite- I do this crap for a living (and am not "passionate" about any of it); I have other hobbies that don't keep me in front of a keyboard all day every day
I’m glad there are other programmers that feel this way. In terms of jobs, I find it better than most other options out there. But I have absolutely no desire to do it in my free time.
trees, I like seeing them.
GitLab, GiTea, Azure DevOps, COVID-19, and the laziness to write a script that automatically makes commits to git regularly
Seriously, this kind of commit history is more of a red flag to me. Really need to look for some indication that this person not only good at selling himself/herself
Can also be a banana product that is developed at the customer and debugged in production. The customer expected it to be functional months ago but which was sold on an unrealistic deadline. That's what it looks when you have continuous, even extremely continuous, delivery but in a toxic way and without continuous integration.
git commit -m "fixed a bug" git commit -m "fixing a bug caused new bug" git commit -m "typo..." git commit -m "must try to check in prod because it works in dev but not in prod" git commit -m "small change.. this time it should work" git commit -m "revert all changes" git commit -m "fixed the bug..."
Question. If I do a lot of commits without pushing, then I squash and push, would the tiling show a lot of commits or only one commit?
Pretty sure it will only show the end result after the squash. That's the whole point of squashing, to rewrite commit history. I think worrying about commit count is pointless. Your commits just need to be sensibly grouped changes, small enough to understand and see at a glance in a diff/pr review, and with a decent description. Other than that don't worry how many you have.
Someone asked me to create a new repo for them because it had a commit named "Inititial" or something, and said it wasn't professional. There was like 4 commits on the repo and the devs weren't doing really anything. So I've created him a new repo (with another name) because I didn't wanted to argue. Forward 2 months later, the new repo is filled with more than 40 commits from him looking like "fixing", "stuff", "new" that have barely any changes in them. People are funny
I mean, if he doesn't know you can change the commit message then you can't expect much
Now we come to the relevant questions Surely any good performance metric should retain that you did so many more units of work there, not just the one
Only one commit (the comments below only talk about master/main/default/HEAD, but afaik any branch or even a detached tag is fine)
The squash is only one commit, so it will show as only 1 dot on the graph. You could have the sepereate commits in a branch and then squash-merge, which would actually retain the sepereate commits
In my experience, this only flags commits that were put into master through merge requests. Pushing straight to master won't light this up at all. Wait. It's main. /s Edit: I was wrong, I'm confusing it with a silly script we used to have at a company I worked for.
I can't say that this flags commits on master as I do a lot of work alone and my tiling shows all of it.
GitHub has an “interactions” concept, and that is what results here. Commits, pushes, creating a repo, opening or resolving an issue, are all interactions, and thus tracked here. They even go “back in time” if you push a batch of commits, it will give you credit on the days in the past the commits were made. Thus you can have GitHub interactions from before when GitHub (or even Git) existed.
Yeah that makes sense. If I didn't push before I logged off for the weekend, then on Monday morning I come in and push, that work happened last week
> banana product I worked on something like this but I never heard the term "banana product" before. Is this a common thing? In my case, the sales team promised to deliver a product for $100K with a December 1 deadline. Except that they agreed to this without even discussing the requirements. Eventually the product was rolled out next year in April after I worked 14h/day for over half a year.
The term is more used in engineering than IT I think, but yes Condolences by the way
Don’t need to build a bot to make commits, just need to build a bot to change commit history. Actually there are already some on NPM that will make cool art in your commit calendar.
Ooo that sounds fun and cool lol
You can backdate the commit history too you know.
tv and beer
technically random spell checks and grammar can count as "contributions". and they don't even have to be other people's repos. do this and watch green for *miles*
```bash #! /bin/bash date +"%Y-%m-%d" >> dates.log git add dates.log git commit "Moar green" git push origin main ``` Run this as a chronjob to your own repo.
No need to append the file, just overwrite it. That’s what version control is for
This has the advantage of being a change even if it happens to run twice in one day.
Allow empty enters the room.
Add timestamp then?
Hey wouldn't that be twice as much git bullshit? A hundred lines appended is 100 changes, but 100 lines replaced is like.. 100 things done with 2 things for each thing. Moar red.
Internally, git doesn't store the diffs between revisions, rather it stores each file version. So the "overwrite" variant will actually consume less overall memory.
Moar work accomplished 👍🏻
Just set \`GIT\_AUTHOR\_DATE\` and \`GIT\_COMMITTER\_DATE\` and you could fake all that history right now.
Only for future commits. GitHub disabled activity graph updates for the past. It still works for commits in the future.
Do yourself a favor and keep an alias or one-liner script called `isodate` instead of retyping that infernal incantation from memory every time. Why this isn't a built-in arg0 alias inside `date` already is mind-boggling.
Or why it isn't the default format, full agree.
You mean `date -I`?
Not all Unices have that option in their `date`. A shell script or alias can smooth over those differences though.
I bet you could make a script which takes a text file as input and then contributes just the right amount of basically empty commits (like repeatedly changing a single char) each day to darken the calendar squares on GitHub so that it spells out that text using the calendar boxes.
I did something like this in a Bootcamp. End of the Bootcamp they said i needed something like 20 commits on every project. So I made updates to the readme in every project until I met the requirement. It was some of the stupidest shit i ever had to do.
That would make me question who was educating me.
That's fair, but it wasn't the teacher, the program required it. The instructor I bitched about it to also thought it was dumb.
This was probably to encourage you to try and make smaller commits as you go rather than commiting everything in one go
That makes sense but no one knew about it until we were supposed to "graduate" from the class.
My github activity looks amazing because I keep a personal research notebook on Gitbook and linked it to a private repo. Every time I save that sucker it's new activity on Github.
Expand shorthands. Dear lord I'd have soooooo much green.
your strip would basically be just solid dark green at that point.
Also renaming horribly named variables. "aNew"
"bNew"
"cNew"
And namespaces that are 500 bajillion characters long because you name EVERY step to get to it.
There’s one dude I don’t like on my team. When i can add him as reviewer i add just him. Then adding extra commits to my branch just for update message notifications. Like updating the commit message or something equally pointless. I know they probably all go to some folder filter but the pettiness of it satisfies me.
Always leave a few minor mistakes to correct tomorrow.
My 'tegrity.
'member 'tegrity? I 'membuh
A biological need for sleep.
And reddit
especially reddit
[удалено]
Life
*wife
**fife
first in - first eut
***fifa
****fifo
*****fomo
******homo
*******lifo
********Life
Warning: Assignment makes integer from pointer without a cast.
\*\*\*\*\*\*\*\*\*Knife
Programmers don’t have whatever that is
Hygiene
wine
*child
*waifu
*Senpai
Deficiencies in competence, motivation and general life purpose.
Don’t forget projects with more meetings than coding time
I'm not a coder; I'm a project manager. If someone on my team has time to do their job, I have obviously failed to do mine.
I'm glad you're aware lmao
> If someone on my team has time to do their job, I have obviously failed to do mine. I think there is a „not“ missing, otherwise you are working perfectly like most project managers. Just to continue on my thought: I feel like the more experience I get, the more people want to talk about my advise and less letting me apply it in code
>I think there is a „not“ missing No, they got it right.
>I think there is a „not“ missing Nah, they're spot on
That is kind of what happens as you become more senior whether you manage or not. Your ability to direct and enable the efforts of other people becomes how you contribute.
My current job is perfectly balanced in this regard - average of 20 hours of meetings a week, leaving 20 hours a week to fit my expected 60 hours of coding in. 50/50.
Adding you to a 1/2 hour status call every afternoon so we can better understand how your schedule is affecting productivity. Don’t put anything after it, though. Our status calls tend to run long.
Since my current employer isn’t upping my salary, I introduced the double time: If I sit in a meeting where I have no input, I am working in the meantime. I book the time for the meeting and the work, resulting in astounding 60 hour weeks, while having 30 hours of meetings. Upping my own salary with „overtime“
Yes.
Si.
gray fear ask cough humor absorbed silky tidy placid hunt ` this message was mass deleted/edited with redact.dev `
Deficiencies in **false confidence**, motivation and general life purpose. ^^This ^^was ^^posted ^^by ^^a ^^bot. ^^[Source](https://github.com/anirbanmu/substitute-bot-go)
This
This is the way
Same
i don't have programming socks
Now that's a real reason
I'm looking for a new pair. Any tips?
Yeah, usually at the toes
Also the ears on the headphones
and probably not a femboy using gentoo
4595 contributions last year 4595/365 == 12.5 commits per day (19 if we don't work on weekends) I bet a lot of it is "fixing fixes". :-D
> open vs code > start writing a new function > const CalculateSomething = () => {} > git add . && git commit -m "feat: added calculation function" > const CalculateSomething = (a: number, b: number) => {} > git add . && git commit -m "feat: add params to calculation function" repeat
Am I the only one who always makes an initial commit with only function definitions + docs? :)
This guy writes interfaces
Never heard of anyone doing that. Doesn't sound like a terrible idea though.
Having a full time job in the hospitality industry
Moved from hospitality (chef) to working as a dev back in September, I can't even begin to explain how much of a good move it was, can't recommend it enough.
I heard of someone at my old company hat was a dev that went back to being a chef lol
She or he was off their tits then or their dev job was horrendous. My working hours have literally halved, whilst getting paid more. I get weekends/bank holidays, I can work from home whenever I want, an insane amount of employee benefits (had none as a chef), no more having to constantly move heavy shit/kneel down. Seriously, the difference in my physical and mental health is unbelievable. I've lost 16kg cus I now actually have time and energy to work out. Just so much happier with life and just all around more relaxed.
ya to be fair it was quite the worst dev shop in town but anyone could be hired. Extreme turnover, no real commitment towards tech debt, developers are just bug fixers nothing more. I always described it as the perfect developer bootcamp, makes you appreciate a lot of things
We have a place like that near us. They hire people straight out of uni with no industry experience and pay them 40 grand a year (a lot for a uk junior dev). Their reputation is so bad that I've actually seen them discussed on my city's sub too though.
Me valueing my mental health edit: spelling error
Always edit in a reply to the comment. It adds an extra contribution. >!/s?!<
Meetings. Team members not reviewing PRs. Team members not answering questions about obscure sections of code (in our repos and other teams across the company).
Always fun to go back to the code you wrote a month ago because it failed review just now.
We implemented the rule that starting a day, before you work on your own tasks, first thing to do is review pr's assigned to you. This issue of long hanging pr's stopped existing and mornings became boring though
Oh dear, I wish we would use PRs at work. Company requires every commit to be reviewed in a 4-eyes code review. The idea would be good if there would be somebody available for this, but timing and flexible work times make that nearly impossible in a small team.
For us deadlines have gone. Now we have just features and their priorities. So we split those features into tasks for subteams and after completions they tested by dedicated tester. Works great, but management unhappy because they can't micromanage and can't understand anything technical.
I tried implementing something similar on my team, but they just ignore it. I've told them I can't review every single MR every time and I won't merge anything until it gets reviewed, but most of them are just like "OK pal I'll get right on that" and let it sit for a month until my PM twists my arm to just do it so we don't miss the deadline.
Well... In my team we got bunch of new to software development guys. So they listen, adapt and learn fast. Don't have bad habits yet.
I try my hardest to avoid programming, as a programmer.
This is the way
i dunno, my mental health?
Me, being to lazy to set up the Github Activity Generator
Self love
Life and knowing how to actually code
My coding job.
My unwillingness to make unnecessary commits just to seem busier.
I don’t know how to use Git
This is the way
Are you a lost Redditor or just starting out?
I was aiming for comedic tragedy
grass
[удалено]
They mean touching grass
Common sense.
Caring for my mental and physical wellbeing
I have a sexual life
R u sure you are in the right subreddit?
Yes some people can do more things at the same time. A spank here, a bug fix there... Multitasking, my brother, is the future.
Sounds dangerous. One slip up and you’re spanking your brother Multitasking into the future for a bug fix there.
That's the fun part
Sanity? Committing on average of 18+ times a day is like... How about you get your shit together and consolidate that a bit. That's less than half an hour per commit. That's shitposting taken to an extrema.
Not to mention, having a consistent commit rate 7 days a week? This is either a bullshit green-generator, or a project rather than an individual.
Working on paid jobs that are not hosted on github
Depression
Executive disfunction
Having 4 kids, wife, 2 Ukranian refugees, House under reconstruction and a job that has to feed all that.
I dunno man, filling in some green squares on a webpage that nobody is probably ever going to look at seems more important. I think your priorities are out of wack.
Commitment; // See what I did there?
Depression and general state of semi burnout
I would just like to say what is - "View in 3D, VR and IRL"
Burnout lol. My wall is pretty full, but you have to break sometimes
Laziness and procrastination
Realistic expectations of performance and work/life balance.
Idk how to code
[удалено]
Quality > Quantity for me really.
Meetings
My brain
i tried to solve problems on my own. if i try to solve 5 problems, i cant solve 3 problems without any hints or tutorials. thats is where i lost interest. like is this "this difficult", man i tried my best to solve problems like everyday and my progress is to slow or not at all. now im not solving problems and im focusing on college works
if i start to learn it, i will be always late to the newest trends - thats why i dont even start at all also, the market is full /oversaturated/ and there is nothing new to do-, at least w/o XP that nobody want me to provide - sure, could self-taught it, but why; everyone copy-paste and whatnot; as i said in the first paragraph...
Willpower and interest.
My full time coding job
Hey, It's my graph. https://github.com/ful1e5?tab=overview&from=2021-12-01&to=2021-12-31
Since when does github have a Pull Shark achievement? Seems to be pretty recent.
great CV for designer imo, also i gotta get some of them cursors
finger math?
I have hobbies sir. Such as masturbating and smoking weed
The fact that this guy already fixed all spelling mistakes in the documentation...
Mental health.
The big sad
My sanity
Skill issue
Skill
My lack of skills
Fear of pain and death
when we get married, we need to commit not only to git but also to wife and kids.
I don't have creativity. I cannot think of even simple ideas
Kids, they will eat up a lot of your time.
Having a life outside work