Over Promise Under Deliver

Content My old Projects waiting for me to finish them Development

Content 1989 It's amazing to think what great and exciting things people will be doing with PC's in 30 years 2020 1.000 T-REX vs 80.000 CHICKENS - Ultimate Epic Battle Simulator

Four years. Four entire years of data structures, algorithms, compiler theory, discrete mathematics, and probably crying over pointer arithmetic at 3 AM. The culmination of this academic journey? A contact form that looks like it was built during a 1998 Geocities tutorial. No CSS styling, default browser fonts, and that beautiful "Select an option" dropdown that screams "I learned HTML in my first week and never looked back." The gap between what CS programs teach and what you actually need to build a basic website has never been more apparent. You can probably explain Big O notation in your sleep and implement a red-black tree from scratch, but centering a div? That's still black magic.

Someone thought they'd escape JavaScript by going to hell, only to discover it was invented there. Plot twist! JavaScript isn't just waiting for you in the afterlife—it's the reason you're headed there in the first place. The real punishment isn't the fire and brimstone—it's maintaining legacy code with callback hell, undefined is not a function, and type coercion that makes absolutely zero logical sense. Satan himself probably gets confused by JavaScript's equality operators.

You know you're in for a wild ride when your "simple console app" throws a System.in encoding tantrum before you even write "Hello World." Nothing says "Java experience" quite like spending 3 hours debugging character encoding issues while your code hasn't even reached line 10. The progression from confident optimism to existential crisis is *chef's kiss*. Started with "hmm today I will write simple console app" and ended up in Stack Overflow hell with error messages that have more workarounds than actual solutions. Resolution: Cannot Reproduce. Fix Version: None. Translation: "You're on your own, buddy." The best part? The error literally says "System.in can't read non-ASCII" which means your JDK decided that anything beyond basic English characters is too exotic for its taste. Welcome to Java, where even reading user input requires a PhD in charset negotiation.

Content You don't have experience for the job But I need a job to get experience Then get a job That's why I am here Go get some experience first