WHAT PROJECTS DO I DO TO PUT ON MY RESUME?? IM A VERY BORING PERSON SO I CANT THINK OF ANYTHING I NATURALLY WANT TO DO

WHAT PROJECTS DO I DO TO PUT ON MY RESUME?? IM A VERY BORING PERSON SO I CANT THINK OF ANYTHING I NATURALLY WANT TO DO

Attached: 1541086803189.png (1920x1080, 110K)

>resume
>projects want to do

son... you need to prove your expertise, not telling what you like... you're not a kid are you?

He obviously is, that's why he's fucking asking

I try to come up an idea where im somewhat knowledgeable but have room to learn more but every idea I come up with either is really simple and a bit boring or really fucking hard.

Like right now im doing image processing, first by creating my own image program that reads in the pixel values into a 2d array and determines image type, etc, then I wanted to like implement object detection from scratch without opencv but it seems really fucking hard now since im relearning all my math from scratch.

I just finished a networking class but idk what to do with that, im just so confused and scared guys, I feel lost

just write down you can fizzbuzz

>you're not a kid are you?
isnt the answer already obvious? what do you get from this blatant ad hominem? are you a kid user?

Scared of what? Just go in with the first thing you do well. Being afraid of the "freedom" of choosing about your future is silly, trust me.

Im just not sure what to program, I figured once im a more competent programmer what I want to do would come naturally but it hasnt. Maybe some inspiration would help, what projects do you guys do for personal use that would make you feel proud to show off?

porn

>he han't programmed an open source fingerbox

lolicon pornography sorter
hentai voice actress identifier
hardcore encryption devices
angry bees

N-no memes pl-please

Attached: DF8BD406-0196-4117-8B09-7ADE68148D28.jpg (367x401, 27K)

Maybe try one of these? If you built anything during University classes put those down, if they're group projects pretend you took the initiative and lead the team, it's not like they can prove you didn't.

Attached: 1539188533043.png (1920x1080, 302K)

Thank you user! My Summer data structures class professor had us program a complete linked lists (both single and doubly) templated in C for an assignment, perhaps the other assignments are good to put too? We also did:
Array based templated queue and stack implementations, graph implementations with different searches/sorting (think DFS, shortest-path, etc) using edges, and templated BSTs and max heap

You probably don't want to bog down your resume with all the stuff you did in a data structures class. It's important that you know the stuff, but i a bigger project that actually makes use of the various data structures will be more valuable in proving your ability to write software. Any other substantial assignment work?

For the image processing class we had to implement a bunch of functionality from scratch that opencv implemented. Like hsi to RGB, various stretching, edge detection, gradient amplitude and thresholding, etc.

"Are you a bad enough dude to encrypt your hard drive with a hammer?

"Giant 1000 degree magnetic hammer vs hard drive"

Damn. I once had to implement an IndexOf manually in Java and it took me like 3 hours.

If you're able to do all that it sounds like you have a decent enough understanding of image processing to try implementing object detection. Read through your course textbooks, any other textbooks and even papers written about the topic. Pretty much any project an undergrad is going to do will have been done before by someone, and it's likely well documented, you've just got to find the information.

Don't worry about the project being too simple, for 2 reasons:
1 - As long as it isn't clearly ripped straight from a tutorial, simple shit is better than nothing
2 - You almost definitely will find ways to make it more sophisticated by the time you're finished with the original inception of the idea

I just finished a semester networking project where we had to implement a server that was protected against replay attacks and reasonably against dos attacks. It handles GETs and the server can only be opened with port knocks and kept open with consecutive port knocks otherwise closes after ten seconds. Would that be good too? Maybe flesh out some more?