I was going to suggest that the author was in marketing and didn't know the difference, but the article seems too in-depth for that. Maybe it's hybrid and devs wrote the more technical sections.
When I lived in London roughly 40% of my salary went to rent. London was actually more expensive, at least for a 1BR with roughly the same distance to the city center, as NYC.
>Why do you want to replace everything with Javascript?
Because a huge number of devs already know it, so you can have your web devs work on your mobile application.
That said, my company tried Fuse out around a year ago and went with Ionic instead. Partially because adapting Angular to Fuse was a lot of effort, and partially because at that time Fuse was not nearly release-ready.
Things like "The bad news: joining Stripe is still a risky proposition." also make me cringe... don't tell me that anyone reading that sentence doesn't realize it's meant to entice them.
Maybe it's not a fair comparison, but contrast with the Valve new employee handbook, which makes it clear what it's actually like to work there and how their culture impacts the workplace.
I'm not convinced, it's assuming a particular interpretation of risk. For people with great employment prospects, a company that still has a reasonable chance of failure is less risky than a safer company where they don't get to develop their skillset. For me, a risky job is one that doesn't make good strides towards lowering the impact that ageism is going to have on my career in a decade or so.
I'm a currently-employed web developer (bootcamp grad) and I'd love to see a part-time (nights and/or weekends), cash up front offering to deepen my CS knowledge. Just throwing that out there in case part-time something you guys have thought about. I'm sure I'm not the only bootcamp grad that could use an in-depth CS program.
Yeah, we think about it a lot. We want to be very careful about scaling into something like that because the part-time dynamic is very different than full-time, and the most important thing to us is our student experience.
It would also be long, if we used the current curriculum. Like... a year long. We're not sure if that's too much of a commitment for most folks, so we're asking.
I'm in a similar boat to the person above (bootcamp grad working as software developer). I have been trying to do a comp-sci degree but that cost, degree requirements (classes unrelated to my major) and actually going to school after work is a major pain. I would definitely pay for a year long (or more) part time CS course if it was intense and online. I'm doing that already, but it would save me a lot of time/money of not having to actually commute to school.
Hey there! We've been doing this at Bradfield for a couple of years, and do get quite a few bootcamp grads (maybe 100 to date) typically 1-3 years into their careers. Which bootcamp did you attend? Ask around there and I'm sure somebody has good things to say about us :)
This is another area where technology is hugely beneficial. Not everyone can move to a city, but people who drive to work could work remotely one day a week. Hell, let's make it Friday, who wouldn't like that? There are few office-type jobs that one just CAN'T do remotely at least one day a week, so you've cut a significant part of the emissions of a significant part of the American population.
And this can be instituted as an economic incentive; employers could get a tax credit or something in exchange for the proportion of work they allow employees to do remotely.
What we really need is WWII-style, society-wide action on this count--remember the days of Meatless Mondays, saving your cans to make bullets, mailing your binoculars to the Navy. Even if it's confined to the parts of society that actually believe global warming is a serious threat, making pro-climate living a social norm could have a tremendous effect.
How about we just take the step and say that eating beef, in any circumstance, is morally wrong? Even if you can find some beef that you think is ecologically responsible, your are promoting the practice which is perhaps most central to global warming, after driving a large gasoline car.
I think if drag and drop builders find an audience it will be in a sweet spot between engineers and clients, maybe used by support engineers or customer success to build and modify applications to client specifications. Technical users will always want more control and in my experience clients are happy to pay for someone else to do the work, even with DND (I've worked at two companies that have built DND form/app builders, neither caught on much with clients).
That's why I don't target primarily developers, but the end-users of such apps. Of course knowing Javascript wouldn't hurt, because it opens a lot of more possibilities to further extend the entire app, but my idea was to make it possible even for non-developers to create apps for CRM, invoicing, accounting or inventory management for their needs. So in my case it's not really visual programming, but a drag-n-drop builder, which also has an integrated code editor in case the user needs it: if they know SQL, awesome - write a custom SQL and it is automatically mapped and available in the forms.
This sweet spot that you talk about between ease of use & flexibility is definitely key.
