I have a feeling someone else is going to respond with some other points so I wanted to touch on something particular:
From my view, I just personally think most folks should be using feature flags and a continuous deployment cycle in general. With that in mind, a lot of what we built was to make it more accessible. We focused on an easier to understand UX, and building tools that were easy to interact with.
But most importantly in that line of thinking, and a major differentiator in my eyes, we tried to make as much of our platform un-gated as possible.
So all of our features are available to anyone regardless of their plan (outside of anything that requires a custom setup or something truly enterprisey).
This means that all of our integrations are freely available too.
We launched https://devcycle.com about a year ago. We're not trying to compete in the self-hosted / on-prem space. Moreso a super simple setup and high flexibility.
Your use case is interesting though, it would definitely fix a lot of headache for people trying to do this via Auth0 directly. Also this just fits in a perfect slot for people starting up a new SaaS platform for sure. Super cool.
Beyond that, who's maintaining it? Are you going to be able to deploy these things across every single one of your systems? Your website? Your apps? In conjunction?
I absolutely understand that you could just read somejson from a cdn and call it a day, but at some point someone is going to have to maintain it and become the defacto feature flag person lol
I agree. I have found that the best use-case is to import existing HTML emails and then modify/add, as opposed to building them directly in the editor.
It is _any_ industry. San Francisco has a ridiculous problem where the city has become so tech-centric that your entire life will be tech even if you try and distance yourself from it. Your friends will all be in tech. People you meet on the street will be in tech. Your uber drivers will pitch you ideas. You'll overhear the next big ICO at every party you go to. Your life is changed by every small startup trying to remove any small inconvenience in your life. And this becomes one _humongous_ bubble within the city. So then you have this entire world that is just completely and entirely oblivious to anything outside of it.
If you travel to cities which are known for specific things, you'll often find these culture pits. SF is just a really special case. Its just the size of the city that exacerbates it so much there. Its tiny. Theres no room for growth. Anyone not in tech got pushed out. And now you have a culture silo.
I specifically moved away from San Francisco to Toronto to avoid this very problem. I'm still in tech. Theres no shame about it here at all. Hell, I get excited if I meet someone also in tech now. The city is so big and has so much space to sprawl and have startups anywhere that tech simply doesn't define anything here at all.
It doesn't have to do with the industry entirely. The tiny city is the problem IMO.
"“You wake up, get the shuttle bus, go to the bubble of campus and order food via an app when you get home. You are not a citizen, just a bizarre leach who makes money,” he explained."
I'm not sure I understand. The whole article is just describing literally anyone in any industry.
What people can't seem to grasp is that tech in SF/SV simply created a massive insular culture that doesn't contribute to the culture that was previously there. It just took over ruthlessly. All previous artistic beauty that was in SF is just gone now and replaced with tech kids that get paid a ton and would rather spend it on cryptocurrencies and music festivals than participating in the city's artistic scene.
Its no wonder at all why people don't like tech people. Its not because they get paid a ton. Its just because they get paid a ton and have no care for anything that was previously there.
But I mean, its a tiny city and the city's building regulations don't do much in the way in helping with gentrification at all. Not sure what else could have possibly happened.
A sad truth that no tech company is actually going to start off with an internal data security and access keys and rules surrounding such things.
I mean, its inconvenient, sure, but damn why is it nobody cares about security until something actually happens.
Question: IS this actually illegal though? Pretty sure if godmode were illegal in apps/sdks, half of the valley could be sued right now. What are the specifications on that?
Back in 2013, there was no big Canadian hackathons part of MLH. We were originally going to call it Hack Waterloo or Waterloo Hacks or something along those lines. But the issue we had back at the end of 2013 is that none of the other schools really knew where Waterloo was.
We wanted a name that people could identify with an area. And considering all of the biggest undergrad hackathons are in the USA, and completely without argument South of us... Identifying as the North isn't really off base.
I believe DubHacks (U of Washington) is the only major US hackathon that is North of us.
Also, who doesn't identify Canada as the North? We aren't just a hackathon at Waterloo. Hell, over half our attendees don't even attend UWaterloo. We're Canada's largest undergraduate hackathon. That's what matters. We're identifying as Canada at a hackathon that just happens to be in Waterloo. Basically, we wanted a name that we could use even if we changed the venue to be anywhere in Canada.
You got pretty bitter over the name of a hackathon. As I said, a lot of our attendees identify Waterloo as being North of them. Because it is. Its Canada.
As for your last sentence:
Does HackMIT sound like a hackathon in which you deal with problems faced only at MIT? Does Boilermake sound like a hackathon in which you make boilers? Does PennApps make it sound like its a hackathon in which you make apps for UPenn students?
Its a name that identifies us as Canadian without explicitly being called Hack Canada because we didn't want to be too overarching as to bother the other hackathons in our Country.
Hey, who knows, maybe we eventually will make a hackathon in the style of WHacks (our 2014 April Fools prank) and call it Hack the North:
http://whacks.info/
I have a feeling someone else is going to respond with some other points so I wanted to touch on something particular:
From my view, I just personally think most folks should be using feature flags and a continuous deployment cycle in general. With that in mind, a lot of what we built was to make it more accessible. We focused on an easier to understand UX, and building tools that were easy to interact with.
But most importantly in that line of thinking, and a major differentiator in my eyes, we tried to make as much of our platform un-gated as possible.
So all of our features are available to anyone regardless of their plan (outside of anything that requires a custom setup or something truly enterprisey).
This means that all of our integrations are freely available too.