#People say a good chunk of graduates cannot write code, how to know if I can?
33 messages · Page 1 of 1 (latest)
probably cannot write efficient/simple code maybe. The actual swe work done at a job is (usually) vastly different than what the majority of CS majors are learning in school
so theres usually a learning curve with respects to how stuff is actually done on the job. Additionally, each company, and teams within the company have sometimes specific code writing styles that you probably won’t know. And other small things, you know when to elect for an array or just a hashset. When is using a stream appropriate. When to extract code and put it in a function instead. Etc etc
idk at what point are u able to say “i write good code” i think other people would probably need to tell you that
through PRs/CRs at a company you work for
on the bright side, graduates are better about writing code than PhDs
Well phds are pure theory i guess. No idea someone takes a ms or phd in cs either way, since you get better at the industry.
I assume so. Thanks for the insight regarding the the different code writing styles. I assume they mean basic coding since you said it can change from team to team. Guess theres no remedy except learn from professional experience
There's a different between being able to write hello world in a REPL and being able to compile a working application.
Plenty of grads don't know git, and the vast majority don't know how to compile a working program someone would pay money for.
I was incredulous when I read this observation from Reginald Braithwaite: Like me, the author is having trouble with the fact that 199 out of 200 applicants for every programming job can't write code at all. I repeat: they can't write any code whatsoever. The author he's referring to is
If you can do fizzbuzz correctly in under 15 minutes without preemptively having worked through a solution, you'll probably be fine
Idk where you live and work but afaik most people where I live that got jobs went to multiple hackathons to practice real world skills, knew at least basic Git, and had a deployed-working application or something before they got a job. Jobs are hard to get nowadays man (Dallas, TX). My university also sent a significant number of graduates out with knowledge in KAFKA and Elastic.
That said, stuff like Kubernetes, HELM, and other DevOps stuff is definitely stuff we learnt at the job. You could argue that this is a completely different field tho, much like QA.
Sure, someone wouldn't pay money for a random application, but I think I would disagree with OP a lot. I think the main issue is that Big Tech hiring is so shit, that they have to idea how to hire capable candidates.
Look at this stupid post - https://www.linkedin.com/posts/tylermcohen_google-acceptedoffer-application-activity-6955593806603837440-9i87
Sounds like you just went to a top university and have that perspective.
Especially outside the US, the bar is much lower.
That might be true. I didn't go to a 'top' university, I wouldn't say, but its up there. I went to University of Texas at Dallas
That is just LinkedIn dude. Plenty of people quietly get hired into big tech without a soapbox post, but you will not see them
I see. Git is a huge plus
Good to know Im not one of them
Gee what a nightmare
It's time to practice programming then. What type of programming doesn't matter a lot - just getting more used to writing code
How long did it take you?
I went up after this and solved two hackerranks.
It took me aroundna year to get comfortable eriting stuff
Tough im not good at those puzzle type wuestions that much
I am not either, but the point of fizzbuzz is that there's not much puzzle to it (unless you don't know about the modulo operator, in which case that's fine)
What are some good indicators someone can code?
As in what to test it with other thna fizzbuz
Havinf projects?
Im in uk and they got me for fixing a bug and answering some questions. Idk how competitive that is
Uni of "state/area" is often good uni
Leetcode easies are an option