Begin a project

>begin a project
>code enthusiastically for 3 days
>encounter difficult part
>lose interest
>realize there's nothing but difficult parts ahead
>lose interest even more

Attached: 1538190656548.jpg (1111x853, 128K)

>begin code project
>code enthusiastically for 3 minutes

Attached: 1514430954593.gif (400x279, 1.78M)

If your code is on github you can ask for help from other people and maybe get a commit to assist.

Attached: box of cox.jpg (1280x720, 125K)

I don't trust they're competent

Review it. It's not that difficult and a skill you'll need anyway.

Not without a CoC you won't!

>encounter difficult part
>lose interest

Nah, the difficult parts are the fun ones. The problem is when you get to something boring, mindless, and repetitive.

>user sorry your code will not get merged
>*throws tantrum*
>sorry it has bad style
>*7200 excuses*
>just rewrite it bro
>*threatens physical violence*
People are the worst

>Not just banning tranny babies
Cuck detected

But that IS the difficult part user

Attached: 389f1a5fb3a360414a20c2dcb2fcbd50.jpg (650x375, 30K)

start by designing a logo first

>The problem is when you get to something boring, mindless, and repetitive.

No, the repetitive parts are the fun parts.

Because then you can come up with some creative solution to remove the repetitiveness.

Enjoy your fizz buzz tier problems.

Enjoy your copy-pasting from stack overflow

Enjoy your banana flavored pudding

Attached: image_9_.jpg (500x636, 89K)

And you are when u can't even finish on ur own?

this thread is now an "op is a faggot" thread.

Attached: doctorsays.jpg (685x474, 88K)

>take someone else's code
>make some changes here and there
>now it's my code

Attached: 1486266917592.gif (250x263, 213K)

You joke, but those kinds of things come up a lot, and it pays to know how to build not-shit solutions for them.

Going on stackoverflow is not coming up with a solution.

Learn to read, faggot. I said "not-shit solutions".

Try not focusing on 1 task. Start jumping around to all of the other areas and do tiny increments. I find that can help with me sometimes. Like jump to a part and just write out how u think the function definitions might end up. Jump to another class and do 1 or 2 functions.

but that's the most satisfying part of development: cracking down stuff you initially didn't know how to overcome

> begin project
> code for 4 hours enthusiastically
> finish the project that would've taken brainlets 3+ days
> increased my IQ points by 50

Not when you don't even know what you don't know.

I'm lazy, I'm not incompetent. There's a clear difference

>a 3-day project is considered a project

>Needing extra time to solve simple problems

Attached: 1483891278001.png (671x519, 146K)

Oh god, no, this design philosophy is horrible. You should be building things you can test as soon as possible, not castles of abstraction. Start at the bottom. Prototype your data and how it transforms, and slowly build abstractions on top of that until you have what you need. Test every step of the way.

You'll still get that endorphin rush from constant progress, it'll go faster than you think, and you're much less likely to find yourself in a situation where you need to jerry rig the hell out of your program because you built most of it before you understood the problem you're trying to solve.

>not thinking about the problems you're solving and how to solve them in a way that's appropriate for your project

>begin a project
>work enthusiastically for 3 days
>overcome the challenging parts
>only easy pieces left
>lose interest

>Implying I'm not thinking of problems and how to solve them with project needs in mind.

Don't fucking scare me further man. For fucks sake

Attached: 452.png (600x878, 598K)

>Start at the bottom
The hard part is figuring out where the bottom is.

Yes, I am implying that.

Attached: 1505838998258.png (900x968, 468K)

I usually start with primitives. ^:)

I'm not interested in your selfies.

>Manages to somehow defeat the difficult part
>Pure bliss

When you get to this part, you do a list and play a game of "destroy the fucking list".

>begin a difficult project
>encounter difficult part
>realize there's nothing but difficult parts ahead
>code enthusiastically for 3 months
>mfw

Attached: fd0a1acd7a205537e68163f71ee48ee8e5157387a9290e9a1b4060c1f207cc75.jpg (626x922, 129K)

Exactly right. Once you have a clear idea of what the problem is you can make specific milestones for yourself. It's all about staying moored.

Be powered by self discipline, not motivation. If the problem is so easy you don't have to think, what rewarding feeling will you gain from accomplishing it? No, the difficult parts are the best parts OP.

Attached: mmorpg_GRINDING.jpg (496x600, 57K)

Solving the difficult problem is fun, if you can't find the problem/a solution then it's just frustrating.

>code enthusiastically for 3 months
>finish
>open Jow Forums to brag about it
>that program already exists
>>better
>>>and was finished in 3 days

me, but not just coding and skip steps 3 and 5.
I should probably be ashamed but stopped caring too

I had to take a Python (intro?) course for my major and when it came to weekly quiz time I couldn't do anything but just sit there and stare blankly at the screen. The TA just felt bad for me and practically did them for me.

Since I didn't start learning basic programming when I was growing up, is there any hope for me to get back into it? I'm not tech illiterate by any means :(

>Manages to somehow defeat the difficult part
>A bigger, far worse part shows up

Attached: 8399677.jpg (720x576, 50K)

Maybe one day you'lll get laid

Fucking time travelers. Go back.

get your brain checked, I've taught my computer-hating industrial engineer grandpa to program and he wrote a grocery tracking/management script and a stock price scraper completely by himself. yesterday he was working on linking RSS and a TTS module to it so he can use the whole thing like a radio.

he didn't do this magically at once, he did it by taking the time to read books, typing relentlessly in a REPL and copying stuff from stackoverflow. be ashamed of yourself for falling behind an old man who's the father of 4 boomer children

>Take the most difficult Jira ticket to impress my co-workers
>Struggle for days and end up solving it within an hour of pair programming
>Rinse and repeat, worsening my impostor syndrome, which is the main source of my depression which makes me consider suicide every single day.

Getting into IT was the worst decision of my life.

Attached: 1533819008658.png (920x900, 443K)

hey thanks for the advice and support

granted I had a heavy accented Russian instructor and a lecture that didn't have any thing to do with the lab each week

Fucking kek 10/10 convo.

>think of hundreds of difficult but cool projects
>don't begin code project

some examples
>pure FPGA/ASIC router to minimise network latency and maximise throughput
>split VPN tunneling so you can still use the Google botnet but download torrents at full speed
>high performance voxel engine
the only things that I find interesting are the things I am incapable of actually building. And everything else already exists and is maintained by either Facebook or some savant on GitHub.

laziness begets incompetence because you have zero or minimal experience in anything difficult

oh and the one project I have that was actually pretty cool and innovative (it enhanced images kinda like waifu2x) stopped working because the REST API was full of bugs and the company isnt interested in fixing it

I don't even know what any of those things are

Attached: 1347526353304.jpg (782x581, 70K)

>FPGA
floating point gate array. imagine programmable hardware, high performance and low power usage
>ASIC
application specific integrated circuit. specialised hardware, but can only be manufactured by big corps.
>split VPN
pretty self explanatory. send some traffic over a VPN and some of it straight to the destination.

I love you OP, that is all.

>begin a project
>code enthusiastically for 3 months
>encounter real users
>lose interest
>realize there's nothing but technical support ahead
>lose interest even more
>support the project for years anyway

is this how Linux got started?

I think it's pretty much everything.

???

Attached: fpga.png (379x209, 102K)

>Start project
>Takes me weeks/months to finish it up
>Feel proud of myself
>Realize someone already did it before me
>It is better than mine
>It took him way less time than me
>Realize how fucking bad I am at everything
>Convince myself that at least it will serve as experience and it will help me to get better
>Try again, same result
I can't do fucking nothing right. I hate you all for being so good and me for being king of monkeys.

Attached: 1500039032965.jpg (1024x700, 111K)

This. I regret going for IT and should have gone for useless major instead. People around me are so skilled, that's embarrassing.

>Practice as much as possible
>Read a lot, genuinely try to gain as much knowledge as I can
>Try to get really involved into everything I work on
>Encounter problem
>Generic guy sits down on a chair
>Plugs in a toaster with a ti-84 display screen on the side
>"lmaoing coding is easy bruh" as he effortlessly solves every problem I have in a matter of seconds
I do not know about you guys, I genuinely love what I do, I don't have that much experience in comparison to most of the people in here, but it is fucking heartbreaking to see that it doesn't matter what I do, how much I practice and how much I keep pushing forward, I am literally bottom of the barrel and that's where I belong whether I like it or not.

Attached: 1526230754531.jpg (640x640, 43K)

U should just focus on what u doing. What does it rly matter if someone is better than u in something? There's plenty of work to do

In this instance what you should redo a project from your early days then compare.
Shit tier artists do it so they can feel like they're improving, I don't see why it wouldn't work for programming either. (Good artists might do it too, I just remember laughing at some deviant art-tier trash that did this)

Sounds like you have zero clue as to what your doing. I suggest quitting programming, cheers.

>he thinks fpga means floating point gate array

It's Field Programmable Gate Array, you NPC.

I know how you feel. It doesn't matter what I make or how much experience I have because no one wants anything I have to offer.

I think I'd be happier just giving up and living homeless. Maybe I'll get to freeze to death this winter.

I don't even know where to start with programming a simple Bejeweled game for Android with some simple modifications like allowing 2 moves per round before the gems' location resets.

Functional Programming Gay Association, you fucking homophobe!

>split VPN
That's not a project that's a VPN config.

What you need to do first and foremost is to understand how game states are modeled. >jewgle online game programming course

The difficult parts are the fun parts. My personal projects run to a halt when all technical problems are solved and all there is, is the grind, tweaks and bugfixes.

How do I program a website like Omegle for android? which doesn't crash whenever you flip tabs?

Guys if I may interest you... maybe you'll find programming games in Roblox more up your alley. You can make quite a lot of money through it.
It can be a really refreshener and life changer. A real distinction in your episodic life.

>robblox

Attached: 1388592921257.png (684x801, 874K)

>start a project
>fuck up
>start over
>fuck up
>start over
>finally get something good going
>don't start over
is there a better feeling

story of my life

You just described my life

Attached: 1536616615354.png (620x450, 62K)

FPGA actually stands for:
>field programmable Gatorade

the Patrician way

The good times will come soon.

Attached: 1527567366836.jpg (500x666, 61K)

Absolute Patricians

Attached: yesaes.jpg (589x766, 581K)

Cringe

op you have to realize that 99% of the time ur stuck you can get unstuck. ok? you have to learn how to beat your head against the wall that's the trick

Start with simple programs then work your way up.