Enough energy enters Earth's atmosphere on days like this one to sustain 7 billion people plus the six-legged majority with room for human technological innovation. We're just not capturing each day's energy with even greater than 50% efficiency yet.
Very nice formatting for the content but it feels like it's missing three chapters on category theory and two chapters each on the AST module and the `compile` builtin after that last chapter on recursion.
Personally I'd lengthen the course with a Section "1.5" on the raw math topics being dealt with (Set Theory and Category Theory) plus ones the student will certainly bump into if they ever find themselves having to deploy MapReduce in production...
It already has a chapter on MapReduce, which is making a few assumptions about where the student is going, whereas teaching category theory is appropriate for where the student is.
Shameless plug but I designed and wrote something for doing this from 2011 to 2015 because nothing like it existed or indeed exists as far as I'm aware.
It's a p2p caching proxy that also lets you edit web pages collaboratively in realtime over a LAN or the internet.
It has a contacts list system and p2p chat functionality.
This project effectively died due to lack of interest and I still have various security concerns about it (Should you break/reimplement Same-Origin policy or break/reimplement the TLS chain of trust?)
The main security concern is that because it decentralises HTTP in-place (existing URLs can now be looked up on an arbitrary number of overlay networks if the original URL isn't providing an OK response) it puts users at risk of malicious actors spamming overlay networks with browser exploits for popular resources like "news.ycombinator.com/".
I hope TBL and co converge on satisfying answers to these problems or constrain their design to not bother with decentralising existing URLs in-situ.
I'm going to say it.
99% of 42s students wont be architects. It's just the reality.
I come from one of these schools, and the best thing you can say about the teaching : It teaches you how to learn.
If you think anything else you learn is how it works in a company. you're wrong :)
No. Like you don't care about one's ability to make some concrete when hiring an architect. It's nice to have, might be essential on some specific projects. Usually won't matter.
I'm sorry, but if architect cannot make some concrete, i.e. he doesn't know basics of his profession, what you expect from him? A house?
Yes, you can hire him, but that will cost you lot of money. There are tons of examples of cheap architect work, e.g. collapsed bridges in the Western Europe.
I seriously wonder about the proportion of architects who ever mixed any concrete themselves in their lives.
Seriously, almost no developer would be able to write a compiler today. The same way I wouldn't be able to build a micro-processor worth anything.
You wouldn't expect any compiler knowledge from most web (back or front) developers, the same way you wouldn't expect much GUI or globally distributed consistent databases knowledge or experience from most embedded developers.
And it's just fine. It's their problem, their limitation, their career, them missing out and, no, in most cases, it won't impact their jobs or the quality of what they make in any way.
Why do you have to have a problem with that ?
Edit: also, bridges collapse all over the world. Tunnels too.
I'm software developer (backend, fronted, cloud, embedded, etc), but it's often very helpful to know how hardware works, how processor works, how kernel works, how compiler works, how network works, and so on, because it's allow me to make my abstraction at top of all these layers to work much more efficient. It's not expected that I will be expert in all that, but it's expected that I will know basics, so I will not make noob mistakes. Are you expecting noob mistakes from architect, which made your home? Or it's ok if he made mistakes in someone else home or bridge?
I'm a software developer too. Mostly mobile and backend.
On the mobile part, most of the clients have pretty much no idea what a processor really is, or how networks work. Hell, I have to explain to them that if they want to build this kittens social network, they're going to need a back-end and that no, it doesn't matter to the mobile apps what language their back-end is written in (and vice-versa).
For most of what these people ask, all you need to know are the basics of Android and iOS's SDKs and how to make API calls. Half the time, their isn't even any networking involved !
I'd be thrilled to work in an environment where this kind of knowledge matters. But like most people I'm stuck working with some people who'll tell you that they don't want to be software developers; it's just a means to an end to them (which is fine. Just don't use that as a shoddy excuse for doing crap), refactoring codebases built by some kids who don't have any software architecture knowledge and don't see the problem in their network layers popping modals and alerts, wondering how on earth a view could end up being a singleton (and no, "I was somehow convinced I needed to access it and change it's properties from this class over there" is not a satisfactory answer) or spend half my day on a single rebase because of some git submodule crap.
So yeah, for most of the people I've had the 'delight' of working with, they are missing so much that no, hardware intricacies, processors inner working, compilers logic and functioning or networking knowledge aren't the critical aspects they're missing.
Heck, I'd be glad if their code was even just readable and had anything resembling an architecture. Or if they didn't turn everything and anything into a singleton whenever they felt like it.
I'm going to stop now. But going back to the architects analogy, if these developers where architects, then most of those I've met can't tell the difference between plumbing and electrical wiring, so I'd be glad if they left the concrete to the craftsmen and at least managed the basics of their jobs' specifics.
Software developer must know how to make good software product.
Software engineer must know how to understand and meet specifications, follow engineering codex, and son on.
And so on.
I'm talking about software developers. You are showing me examples unrelated to professional software product development at all. Moreover, there are lot of professionals in IT, but only part of them are software developers.
So we are just talking about different things: you are talking about "someone who sits in front in compute and enters programming code", while I'm talking about professional Software Developer, short segment of IT professionals, subset of programmers.
You are pretty much making my point, you know that, right ?
I'm talking about people who are one of the or the only persons with any technical knowledge in their companies, who's job it is to interpret and understand whatever the requirements are and deliver on the products, wether it's apps, web or mobile, back-ends or both.
They need to know how to make good software products, they definitely should know how to understand and meet specifications, etc, etc, etc. They just don't. And yet, they have the positions they have. And what they're most lacking, contrary to the point you were making earlier, definitely isn't compiler theory or the ability to build shell scripting parsers, but the very abilities you just listed.
So no, we are talking about the exact same thing, you just seem lucky enough not to have encountered this kind of people in that kind of position, and I'm glad we have finally come to an understanding.
Of course, I know such people. They are called "anykeyers" in my country. And of course, they are not software developers or software engineers.
If they have no education/training adequate to their profession, they are just amateurs. I trained about few dozens of them during my career.
We have outsourcing industry in Ukraine, so "Software Developer" is well defined term here. Somebody cannot sit five years playing with Excel, or JS/HTML, or mobile apps and then pretend for Senior Developer salary. Inexperienced (junior) developers causes lots of problems to project and must be supervised by a senior developer. We work on tight budgets, so we have no time to play name games. If someone has "developer" in his title, he must meet expectations for his role. Otherwise, project will collapse and everyone will suffer.
