Bro I’m in final year and literally know NOTHING, am I doomed? 😭

[email protected]

If you survived university this long, you must either be really good at cheating or you have imposter syndrome. My now Ex-wife graduated in a medical field 10 years ago, and the first year of her job she thought that she doesn't know enough. Then she realized how the others around her worked, and came to the conclusion that she had enough knowledge to use her critical thinking and to know where to look something up if she didn't know it. In the working world, noone has an issue with you looking something up you don't know by heart.

Also, i can only mirror what others here said - get on Github and find a project that interests you, or try modding a game you really like; It doesn't only mean you get practice, but also gives you the self assurance you are currently lacking.

[email protected]

You'll learn more on the job than you did at uni, I sometimes have small projects that I hire out, you can reach out to me and try out a paid contract job with low pressure. I've helped a few other people through the same process but no promises.

The industry is moving very quickly, honestly don't stress too much about the nitty gritty details like syntax and such, probably a safe bet to focus on the practical side instead of the deeply technical side.

Every interview that I've given and taken has been more about personality and compatibility than skill.

[email protected]

There’s always McDonalds.

[email protected]

Find an open source project that's coded in your language of choice that you both care about (edit -- or that looks interesting to you, at least) and want to add functionality to.

Download a working copy, then, since you're learning with this, pretend the repo doesn't exist anymore and you're on your on with your self-imposed assignment.

Figure out what functionality you want to add, start with changing or augmenting something simple, and figure out where that would go in the existing code, and make it happen.

See if you can manage to Google search your way past any errors you run into, preferably alternating between ai answers and things like stack overflow posts, only instead of copy-pasting the code that errors out (or the solution code you get from ai or posts) actually step through things and figure out what the "solution" code is doing differently and ask yourself why and how that makes a difference or has a different effect from the code that generated the error in the first place. Then decide whether it's actually likely to fix the error or not. If you think it's going to? Try using it.

If it works, make sure you understand why.

If it doesn't, try to figure out why not.

Keep going until you have a working new feature.

Then try a more complicated feature.

After a few of those, try tackling some of the bugs in the repo.

[email protected]

That's my favorite thing about switching jobs - low expectations!

However, I don't like how the training these days is usually "read through some old tickets, you'll figure it out, see you in a few days!"

[email protected]

Lots of advice here but I haven’t seen anyone mention coding boot camps. There are free ones like FreeCodeCamp or lots of paid options. You can do these to learn or validate what you have been taught.

My company hires associate-level software engineers directly out of college programs and boot camps. They don’t expect people from these to know everything; you may not have ever even used the language that you will be expected to code in! But by completing a program you’re showing you understand the logic of programming and that is applicable knowledge.

Look for entry-level jobs and you’ll be fine. Even better, look for companies that intentionally hire from programs like yours. They’re more likely to have internal programs to help teach new-to-career folks.

[email protected]

"Gifted" but not quite genius kid here. I managed to coast through the first year of University, but then I hit a wall, where discipline and good study habits would have served me well.

Eeexcept I'd never needed to do that before and I had undiagnosed but pretty blatant and crippling ADHD which meant that I couldn't do that even if I tried. (I occasionally did try. No dice.)

Repeated the second year. Barely scraped through it. The decline continued. The final year I was just showing up because that's all I knew how to do and was too scared to up and quit.

Spent most of my time in the computer labs interacting on the early WWW. It was an excellent distraction from the absolute stress I was under.

Didn't graduate, but heard you could get a diploma for having passed the first two years. Requested and got that. No ceremony. No fanfare. It's in a picture frame in a pile of stuff somewhere around here. Too many painful memories to display it on a wall. I still have nightmares.

What I did do was go out and get a job. This was pre- turn-of-the-century so getting a job was way easier than it is now, but it still took six months. Ended up working for what is now a fairly big US-based company that shall remain nameless. (I was ousted long before they made it big.)

My advice would be to do similarly. If you don't think you can knuckle down and do what you need to in order to pass this course, get out now, or else at the end of the school year when there's a natural end to things.

BUT: Do at least try to knuckle down first. Lots of other good advice here. Maybe you're not in as bad a state as I was. Maybe you do in fact "got this". Getting and doing a job is different, but it's not necessarily easier. (But for me that's another story.)

[email protected]

Eh, I thought I was OK going into my career out of college only to find out I learned more 3 months on the job than I did in the classroom. About the only practical experience I got in college was in labs setting up environments. So don't sweat not knowing. You'll get direction in an entry level position, then you can work on your own stuff, or you can find a topic that interests you and work on it on the side like a video game or tool or website. My current side projects usually help me in my current career. So I picked up a skill that I never learned when I exited my first career (docker administration) and I feel like a goober for not learning in the past.

I know why i didn't learn it though. One, two, skip a few, after burnout and changing careers, my skills look like they could come back in fashion for moving stuff back to on premise and I could be useful again (IT) especially for small clusters, networking, and specialized local application support, so at least I have a backup plan for when AI takes over my current line of work.

I guess my point is the job is kinda like a better one stop shop that pays you to learn the specifics whose bosses should get you the guidance at least with incentivized goals; money.

[email protected]

You're studying to be a programmer, right? You don't mention your comfort language, so I'm going to try to keep this language agnostic.

Here's what you do:

Figure out the absolute simplest application you could possibly build. I'm going to suggest a to-do app, because it's traditional and it's a dead simple concept.
Figure out the absolute simplest version of that application. I'm thinking it just renders a hard-coded list of to-dos with exactly one piece of interactivity, a button to cross off an entry.
Add another piece of interactivity: Make the rendered text of a to-do entry editable.
Add another piece of interactivity: Make the list resettable, so your edits and cross-offs vanish.
Add another piece of interactivity: Make it possible to add entries to the list.
Add another piece of interactivity: Make it possible to turn the list green.
Add another piece of interactivity: Make it possible to remove entries from the list.
Keep adding visible features until the frontend is the best goddamn to-do list you can make.
Create a backend. Your backend has a database (such as MySQL). It has one table, which contains every to-do.
Your backend should expose a REST API. If you don't know what that is, read up on it. They're very simple. Long story short, it's a means of sending and receiving structured JSON.
Here's where your app gets real: The REST API can read from and write to the database. That means no more hard-coded entries on the frontend. Your frontend will now read from the REST API when it loads, and populate the to-do list from it. When you delete an entry, it will be removed from the database. When you cross one off or turn it green, it will change in the database.
Congratulations, you've built a rudimentary real-world application!

[email protected]

I felt the same way you do when I was in my last year of college. I remember being really nervous about it and thinking that they didn’t give me any real world experience, but you’ll get that when you find a job. The job I got out of college was in a programming language that was so foreign to me (and probably most people) that I had no idea what I was doing, but you end up adapting and using the constructs they’ve taught you.

I’ve been working in tech for 24 years now and still feel like I don’t know enough for my job most days. The good thing is that it’s a constant learning experience I guess.

[email protected]

Start it all over. Do things right the second time.

[email protected]

Keep your mouth shut, and fake it til you make it.

It's what EVERYBODY does. That is literally the key to life that nobody tells you when you are young.

[email protected]

Tech executive here. The likelihood of you being able to compete as a developer in the current job market when you cannot demonstrate skills, knowledge, or showcase your previous works is negligible. That said, you have access to the internet, FOSS, Git, presumably test environments at your school, teachers and fellow students to ask when you need help, etc.

Find a bunch of problems you'd like to solve or features you'd like to see and spend the next year cranking out projects. Make sure you have a portfolio fo projects that required multiple skillsets to achieve.

Also, there are a lot of free courses and even some certifications out there. AWS, Azure, and GCloud have all sorts of training available for free. Take some and use those skill to run some projects in cloud environments.

CONTAINERS!!!

EDIT:
The best position you can be is one where you don't want a job because you want to build your own thing. Be so good that companies want to compete to hire you away.

[email protected]

Sounds like it's time to start some basic code camp / code academy / Udemy courses in your off time to catch up.

[email protected]

Senior UI architect here. I didn't know shit about crap when I graduated college as far as programming, and I was on the fucking Dean's List and graduated with honors. 95% of what I know I learned it on the job after college. Today I work from home and have a comfortable income so don't let your fears take hold. You still have to study on your own creating personal projects which will teach you way more programming than what you learned in college.

[email protected]

The fact that you are questioning yourself means that you have the ability to introspect. I work at a major university and hire/manage people of all ages--as young as 15 and as old as 65. I have seen all kinds from the super smart and motivated to those who will sit in their position and do the minimum until they retire or those who are so incompetent or incapable of learning that they wash out of their own careers.

You probably compared yourself to that small number of people who did robotics club in high school, got into the elite CS/CE program, and already have a job offer from Meta for $150k. Don't do that, those people aren't normal and have never learned to just live. They also tend to experience constant and unending anxiety, which is why they drive themselves so hard. Do you really want to live that way?

I am always looking for that person who questions themself. If you are concerned about your ability to do something, you will put in the time to make sure that you do it well. If you have a Dunning-Kruger thing going on, then you're going to be a terrible employee and I will eventually resent you and find a way to get you out of my department.

My advice:

accept that you will suffer some form of imposter syndrome for life. This is fine--it is better to be a bit insecure than a bit overconfident. You will constantly work to make sure that what you output is the best quality it can be simply because you are worried that it isn't.
accept that you have little experience in your industry. You're not supposed to as a new graduate. The whole point of your training has been in learning how to think professionally and approach a problem academically. Once you have that basis, you can learn the details.
be kind to yourself. You're your own person and you don't need to use others as a metric. Avoid the "I'm supposed to have..." sort of thinking and just do the best you can.

[email protected]

Yeah that’s actually reassuring to hear . I keep hearing people say the real learning happens once you’re on the job, but the scary part is getting that first break. That’s why I was thinking — if there was a space where you could practice by picking up real projects (even buying ready-made ones just to see how things are structured), get some guidance/mentorship, and then slowly start putting out your own work… it would make the jump way less intimidating. Feels like that kind of model could really help students like me who are starting late.

[email protected]

Yeah, true — programming isn’t really something you can fake, especially in a competitive market. If the fundamentals are weak, it shows during interviews. And you’re right, a lot of people with decent knowledge still struggle to land jobs these days, so for someone who coasted through college it feels extra overwhelming.

That said, I don’t think it always has to mean a hard pivot away from tech. I’ve seen people catch up when they start small: buying or downloading existing projects, breaking them apart to see how things actually work, then slowly tweaking/building their own. Pair that with mentorship or guidance from people in the industry, and it creates a shortcut compared to trying to figure out everything alone. Even if it doesn’t guarantee a job, it at least gives you a portfolio and confidence to back yourself.

For those who decide to pivot — HR, ops, etc. like you said — fair enough. But I feel like having an option in between (learn + build + guidance in one place) could really help students who don’t want to give up on tech completely.

[email protected]

Does your area have any tech meetups? Maybe get out there and talk to people?

For our area, there are makerspaces that curtail to such events. And if you are still lost, there are places like freecodecamp that help out with building your first projects. It has a discord if I recall as well.

GL! Its a VERY hard market right now.

[email protected]

learn to pass a coding interview. practice the common data structures, focus on one language. hackerrank, leetcode, pluralsight.

they don't care about what you learned in school. school is where you learn to think, and prove you can work hard. i never graduated

agnos.is Forums

Bro I’m in final year and literally know NOTHING, am I doomed? 😭