What basic knowledge should a Software Engineering grad know after graduating?
How to write software.
>>55156908
in what language?
>>55156974
English preferably
This question might be better for >>>/g/dpt
>>55156974
that is one dumb question
>>55156974
The fucking language they teach you in school during your Software Engineering courses, dipshit.
also >>>/sci/
>>55156996
>>55157002
>>55157004
>>55156875
The willingness to learn obscure shit because the company you're working for wants to be on the bleeding edge.
>>55156875
Every problem is solvable if you keep digging.
Acting like you don't care about the team is one of the worst things you can do.
It's better to have done your homework and be wrong after legitimately trying, then it is to dick around and change a couple things and have it work for reasons you can't explain.
It'll seem like senior devs are nitpicking constantly but those minor details are important in the long run.
>>55156875
software architecture.
object oriented paradigm. functional, event driven, etc.
doesn't matter which language, should be able to apply knowledge to any language.
>inb4 c++, Java, gc, optimization
that's the programmers job. the engineer is there for the architecture and creating value for the company.
FizzBuzz.
>>55156875
English
*[...] grad _have_ after [...]
>>55156875
How to use a dildo.
>>55156875
>Software Engineering
Programming
>>55160638
>nitpicking semantics to make others feel less important
You're fun.
Virgin is a really good choice now that they've made their routers use 5GHz and AC. The old superhub was shit.
And VM speeds are really quick
>>55162611
thanks
>>55157270
http://imgur.com/gallery/vqUQ5
social skills
how to add value to a business
salesmanship
how to work like a slave while producing like an autistic savant
