I wouldn't call these secrets. Source control isn't a new thing, we've had source control since before I was born. I think chances are if you're taking a course

I wouldn't call these secrets. Source control isn't a new thing, we've had source control since before I was born. I think chances are if you're taking a course for programming, you'll already know to use source control or quickly find out about it. I am confused. The article says developers need to learn regular expressions and then goes on in the next point to basically say libraries have made regular expressions irrelevant and that you shouldn't reinvent the wheel. I rarely ever need to use regular expressions, I don't know them that well and it hasn't prohibited me in my career. Maybe before the Internet existed and we didn't have StackOverflow would it have mattered, but I can find an answer quicker Googling than I can thinking it up sometimes. I partially and respectively disagree with point number #5 the database landscape is a lot different than it was 10 years ago. We have numerous choices now like NoSQL derivatives, graph databases and more. You don't always need to write SQL and flat file databases aren't dead, isn't that what SQLite is? I still use SQLite in some cases because it's convenient. It's not uncommon to find yourself on a project that doesn't need SQL queries at all, and these days if you use something like Ruby on Rails or Laravel (PHP) in combination with MySQL or Postgres you'll more than likely finding yourself using an ORM and not writing queries at all. It is how it is. Point #6 — if you're a decent developer nowadays, I would hope you either pick something like Sublime Text Editor or Vim. I don't think teaching students what IDE's and editors to use should be in a curriculum. Everyone works with what works for them. As long as you can achieve the desired results does it really matter if you're using Notepad? As long as you can write code without a WYSIWYG, I don't think it matters if you used a typewriter. The development industry is time and results focused, not tool focused (at least not in my experience). The whole point of a degree is to teach you the underlying concepts of programming. You don't get taught how to interact with a client, you don't get taught teamwork and I think that is okay. Some things are better left to the real world, nothing educates you faster than a real world situation. You learn the most important aspects of a programming job when you're on the job. Every workplace is different, you can't account for all of the unplanned and unexpected variables that come with a job in an industry like ours. At the end of the day in a programming position you're nothing more than a talented Googler with an understanding of the basics. I don't know everything about my chosen languages, I do however know what to search when I need an answer to a problem I am having. It's all about knowing what to search a lot of the time I find.