Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple's Everyone Can Code Curriculum Expanding to Schools Serving Blind and Deaf Students
- Thread starter MacRumors
- Start date
- Sort by reaction score
If everyone can code, everyone should code. If you want higher wages, you should have something differentiating you from the rest, not exclusionary practices.
It's nothing to worry about anyway. The reason to teach people to code is that it's going to be a common skill soon, just like how everyone uses Excel today. They aren't going to be writing apps or server logic.
[doublepost=1526603544][/doublepost]
Then don't get bad hiring managers. It's super easy to tell when someone's code sucks. And if anything, with more people knowing how to code, the actual pros will strive for better quality. I feel like there's tons of garbage code out there from years back, most of it in PHP, with even some big frameworks like Laravel encouraging it.
Last edited:
In Austria/Europe it's forbidden by law for corporations to advertise in schools. But then, what do we know, we don't even have mass shootings...
It isn't that simple. The CEO hires people below him, and very often he has no real way of knowing what kind of job they're doing. In some areas, he can know from results. Does he know that the software bugs the company has been experiencing are due to poor coding practices and not honest development mistakes that any dev would make? Nope. He also has no way of knowing if anyone under him knows more than he does, since it's typically not the CEO's job to know. So long as the dev is competent enough to keep the company going, he gets by, even if his code is terrible. That's the real world, and it's quite common.
What would be nice is if Apple can teach a language like Python or JavaScript that isn't proprietary to Apple so that "everyone" can contribute to the world and not just Apple.
There have been various tools that allow people without the use of arms (or legs) for typing to use computers, including programming, since at least the early 1980s so I wouldn't be all that surprised to see your co-worker in action. No, my worry here is that the tools for blind kids are going to be completely non-intuitive and just frustrate the kids to no end while really hammering home the disadvantages their disability is going to cause them for the rest of their lives.
In other words my worry is that this could be a well intentioned act meant to help disadvantaged people that only frustrates them and reminds them of how disadvantaged they are. A well intentioned act that only makes the people it's supposed to help feel bad about themselves and their future.
While I am relieved to hear about how much things have advanced when it comes to accessibility tools for blind people (last time I really looked into it was a bit over a decade ago) I'm still worried about the additional obstacles and how unintuitive a lot of the things you mentioned having to do are. More power to people like you who can put in the additional effort to climb all the additional hurdles that blindness puts in your way. However the worry I still have is still that most blind kids who get access to this will simply be put off by the additional hurdles (learning to program isn't easy for people with vision either) and the whole thing just becomes a source of frustration that hurts their confidence and self-image.
Again, I don't want to sound like a you-know-what, but could I make the suggestion that you break up longer messages into multiple paragraphs? Because a long post like that in a single paragraph is a tad painful to read. Just a suggestion thou as you seem to be using a speech to text system judging by how you called Perl "Pearl" with an "a".
Outstanding post.
As long as they're learning some core concepts, it'll transfer to other languages/platforms, I mean, this is mostly just for some exposure, if a kid really gets interested, there's plenty of resources to pursue this in more breadth and depth.
The bold = exactly the CEO's job, seriously, any CEO worth their title would be vetting a director position that they have 100% confidence in to manage the development staff, and if it's a company so small that you've got developers reporting to the CEO, there are several mechanisms to mitigate risk (and if it's a tech company, the CEO probably has decent technical acumen).
At least that's what my 30-ish years as a [some would suggest, successful] CEO, CTO, developer, architect, writer would lead me to believe
Unless the CEO is a developer himself, he can't seriously know how well people under him are doing, and mostly has to take their word for it, and look at the results at the end of the quarter. As I said, so long as the devs are "good enough", the results will be there. That doesn't mean the devs are actually good, though, and the CEO, who isn't a dev, will have no way of knowing.
Well, until there's a major issue with their code that hurts the company. Then he'll figure he has to hire new people.
Last edited:
He shouldn't need to, or possibly even want to, that's why his job should be this:
I'm not sure the company structure you have in mind, but if you have development staff, I'd imagine a certain minimum size that should easily justify a very senior, highly qualified director/VP/<something> to keep things on the rails.