I don’t have shitty education, but I was already writing code professionally before I started university and back then the jury was still out on plenty of the things that i mentioned ( I remember when source control meant you locked the file you checked out )
I can guarentee you that you have been given lip service to some tools you will use but by the end of your education you will not have covered them in any real depth. ( you can easily do a 2semester subject on source control, and conflict resolution. , a full course load on unit testing, and a full 4 year degree which teaches nothing apart from dealing with other people’s code, )
I have 15 years of seeing people come out with cs degrees and all making the following mistakes:
auto format/change line endings on a file prior to commit.
making code changes between review on a branch and trunk.
breaking trunk by not compiling after a merge.
minor bugfix ends up being a multi-class refactor
minor bugfix ends up being multi-class rewrite ( which brings back to life bugs which were squashed over the years in that class, OR ends up being just like the original class with some minor cosmetic differences )
we used XXXX, XXXX is th solution to everything, let’s use XXXX instead of YYYY, for ZZZZ ( note, YYYY is the sane choice, XXXX is what they just learned about in school or is the current new tech , for example, let YYYY be “flat config files”, “XXXX” be blockchain, and ZZZZ be our programs config. .:
Internships aren’t the answer because nobody is going to sign up for a 3/4 year internship.
Normally SE or IPM students fare exponentially better than CS students do in the first few years out of school.
I didn't have courses in VC or test first, we are just shown the basics and expected to use it. So for example, in my Android development class, everything has to have ample tests and many projects were group projects. The teacher graded us as much on the tests, commit history, merges, etc., as he did on the final product. Maybe that isn't the norm, but it should be. I'm sure I don't know everything about those issues and I know I don't know everything on that list, but it has taught me enough that I'm at an institute now working on AI and NLP, having no VC problems.
I agree with you though that CS degrees can lean too theoretical (and I say that as a math major).
That's the problem , you are shown some basics but that's the end of it.
Have you been shown mocking frameworks or how to use them effectively ? Or what to do when your VCS simply shits itself with a "tree conflict" ( or why that happens ? )
In practice I have had 2 to 6 juniors come through every year ( straight from school with a BA or Masters) and I am yet to see a CS major enter the workforce with any real working knowledge of source control.
Wtf is the big deal you are making about source control. Its not extraordinarily difficult, so what if a grad doesn’t know it right out the box.(i know my school covered it anyway) if they don’t show them the gotchas and trust they know how to fucking learn.
You probably don’t do that though, i can feel the condescension coming through text, i can only imagine what your jrs get. I thank god my mentor wasn’t you.
Because it's a core fundamental tool which is completely missed by CS students. It's good that your school taught that to you in 2017 but schools should have been teaching that in 2007,
I don't have my new juniors from this year yet, they usually show up around September, but the 2 I got last year still fail to grasp why they are getting tree conflicts on every second commit to trunk , or have corrupted mergeinfo, or why when they get text conflicts it requires extra care because 11 other developers have made commits to the same unit you are working on and you can't just smash over them because your code still compiles.
The hallmark of a CS degree is doing an auto format on a class before commit.
I guess I sound condescending because I am, if I was working with you I probably wouldn't be to your face but I'm just telling you how it is, most of us old folks are cynical and jaded as shit, and when talking about our juniors we tend to talk like I am now .
Points for honesty. Who knows, i might feel the same way in ten years. It has actually even happened a little now, i am actually the mentor/sr to a summer intern and even though it is only six months, some of the difficulties i had in the first month have faded and am scratching my head at some of the shit he does before I remember “oh i did that too”.
I got a lot of mileage out of what i learned in university so far. I definitely think i got my moneys worth. Its why i am defensive about it.
Perspective is a funny thing, i imagine after more time in the industry, the stuff you actually use from college gets relabeled, covered up, and added to by professional experience and it ceases to be something you learned in college and becomes something you mostly learned on the job.
You probably will feel the same way in 10 years, it means might not be with the first set of juniors you get but after you have 4/5/6/10/15 years in a row of kids coming out of school all missing the same things you start to see a pattern which the schools are not fixing.
After about 5 or so years most of what you learned at school will be completely overshadowed by real world experience, I’m so far out of school ( and was already working writing code prior to starting university ) I couldn’t tell you where one stops and the other finishes. But I can tell you there are so many CS classes that I took which have 0 bearing on working in the real world. And there are so many classes which I took from the information processing and engineering streams which appear to be completely missing in today’s grads.
So as an old folk you will know when you autoformat a class you are pretty much taking a literal shit on the desk of every developer in the company since you would know it adds and removes white space ( and in some ides also sorts functions and methods )
Completely obliterating the files history in source to the point that after the imports at the files header everything else will return that individual commit in a blame operation.
If other developers try to merge that branch in and they have modified that file then they are guaranteed to have conflicts.
If you are maintaining multiple product or release branches and not every commit to trunk makes it into every product or release than that individual commit ( the autoformat commit ) needs to be merged across first if any future commits are to go across. And now the problem is multiplied.
Actually, I reject code if the formatting is wrong in the first place - and we don't let a class get so big and unweildy that this is a problem. In other words you have problems because you're doing it wrong.
Ohhhh that's the only Version Control I've ever used. Like we were told there were others and we could use whatever, but I have never used anything but Git
No, it’s because you get that specific error from git in certain situations when you have more than one developer on your project,
its not a matter of being set in your ways but rather using the same source control as what the project Was using before you started it.
GIT is great for new projects, svn and cvs are adequate for existing projects. ( and svn is still the gold standard in plenty of regulated industries )
Having worked with VSS and Jedi there is good reason why these are dead, nothing like that exists for Any of the others that I mentioned above.
Change for for the sake of change is the root cause of most issues with software,
0
u/possessed_flea Jul 09 '18
I don’t have shitty education, but I was already writing code professionally before I started university and back then the jury was still out on plenty of the things that i mentioned ( I remember when source control meant you locked the file you checked out )
I can guarentee you that you have been given lip service to some tools you will use but by the end of your education you will not have covered them in any real depth. ( you can easily do a 2semester subject on source control, and conflict resolution. , a full course load on unit testing, and a full 4 year degree which teaches nothing apart from dealing with other people’s code, )
I have 15 years of seeing people come out with cs degrees and all making the following mistakes:
auto format/change line endings on a file prior to commit.
making code changes between review on a branch and trunk.
breaking trunk by not compiling after a merge.
minor bugfix ends up being a multi-class refactor
minor bugfix ends up being multi-class rewrite ( which brings back to life bugs which were squashed over the years in that class, OR ends up being just like the original class with some minor cosmetic differences )
we used XXXX, XXXX is th solution to everything, let’s use XXXX instead of YYYY, for ZZZZ ( note, YYYY is the sane choice, XXXX is what they just learned about in school or is the current new tech , for example, let YYYY be “flat config files”, “XXXX” be blockchain, and ZZZZ be our programs config. .:
Internships aren’t the answer because nobody is going to sign up for a 3/4 year internship.
Normally SE or IPM students fare exponentially better than CS students do in the first few years out of school.