|
Version control, version control, version control. And not just the simple basics, give them weird situations where they have to actually resolve merge conflicts and cherry pick and the like. Much better to learn that in a learning environment than when prod accidentally gets a 6 month out of date commit on it somehow. And basic working knowledge of the command line, doesn't have to be super in depth but you'd be surprised how many people I work with that get deer in headlights if you ask them to just run a powershell script from the command line. Package manager knowledge is probably also good to know but might not be covered much by your standard Java based curriculum.
|
#
¿
Jul 28, 2022 17:08
|
|
|
|
| # ¿ May 18, 2024 02:48 |
|
|
Cybernetic Vermin posted:"package manager knowledge"? like, is there a single bit of information in that which generalizes beyond the particular package manager the course picks? Yeah pretty much that, you'd be surprised what people never pick up in school. That and the general idea behind inspecting your dependency chain and versioning and such, why you would want to freeze your dependencies in production and the like.
|
|
#
¿
Jul 28, 2022 17:32
|
|
|
Cybernetic Vermin posted:pretty much what? lets say we spend 4 lectures and one lab (say 12 hours of work) on learning the cabal+hackage, what would you put as the learning outcome potentially useful for a job at your place? how do you set an exam for those outcomes? Oh sorry, I completely misread your post. I guess I mean like, how to judge if a package is trustworthy based on usage, best practices for analyzing whether it's worthwhile to bring in a package, checking to see whether it's actively maintained, critical thinking around using your package manager. Can you tell I have to work with npm a lot?
|
|
#
¿
Jul 28, 2022 17:43
|
|