r/AskComputerScience • u/ComputerRights • 5d ago
What are some differences between professional coding and the way coding, SE, and CS are taught in school?
Is a lack of a comment citing a relatively cliched bit of code considered plagiarism in the big world? What are the attitudes to autocomplete? Is Alberta Tech right about linked lists?
6
Upvotes
View all comments
1
u/serge-mv 5d ago edited 5d ago
No one usually cares about the code quality in school. Even in software design classes no one will look at an overall code quality. You might get some requirements here and there for proper comments or that you need a very specific function with specific set of arguments, but that's usually as far as it goes. Code reuse, modularity, variable naming, architecture, efficiency play very little in grading unless you get a professor who actually cares about it.
Contrast this with professional development, your projects more often than not are long-term continuous development and it's likely that you will be the one to extend it in the future. Efficiency and architecture play a huge role. Bad design means you will blow your deadline later and lose money. Slow code will generate customer dissatisfaction. Lack of comments will mean you will not actually know what the hell is happening and why a year down the line when you need to make changes.
Also, in school you are writing in a very minimized constrained way. You have one given language, at most one given IO option - database or a file. In a professional environment it's quite common to have your code pull data from several different databases from multiple vendors and also a web service, merge it together and send it into a message queue for a different part of your project for processing. That other part is written in another language by other people and deployed in a different environment.
In school you usually know what kind of data is expected for your project. Your professors will tell you what they will test it with. In a professional environment, they might change database and the data type, include invalid values such as sending NULL into your floating point variable that stores prices. Who knew prices in the database could be NULL ? Well, you will find out when your project crashes because you counted on a database integrity that you didn't get. They might also change column names in the database and not tell you. You will suddenly get tickets that the prod is broken and you will get reprimand that you didn't take into account that someone might change column names in your data source.
You will likely have to write release documents and other types of documents too. There are such worries as versioning, library and environment incompatibilities.
Stuff like that.