rmanalan

I've been a dev advocate since 2008ish and before that worked in pre-sales (mostly crafting custom demos and prototypes for prospects and existing customers). In my early days as a dev advocate, I was hired into marketing and most of the work was public facing (blogs and conference talks). But then that role soon moved into an official Dev Rel org where we did mostly 5 things:

1. Build and maintain a plugin SDK and integration framework

2. Help write docs and guides (we had a dedicated tech writer in our dev rel org)

3. Do public facing stuff: blogs, conference talks, participate in hackathons, etc.

4. Plan and host events: company developer conference, hackathons, meetups, etc.

5. Write code... could be anything... sample code, tech blogs, integrations, bug fixes to product, new features in product, etc.

It was a hard job in the early days -- lots of context switching. Those who were well suited for it were devs who communicated well, knew how to tell a story, and loved the hustle.

In the past several years, I've seen this role evolve a bit more to be what the author of the article describes: basically dev advos with a social status who speak at conferences a lot. While I think that's an important aspect of a Dev Rel org, I think a Dev Rel org should have a healthy balance of people who are good at the public facing stuff and those who are highly technical and can get in the weeds with other developers. A Dev Rel org with that combo can deliver high-level and visionary stories to the public and also dive deep into the tech with any developer/architect in the industry.

With the pandemic, we're having to reinvent ourselves yet again and trying to figure out how to get the best signal-to-noise ratio with our audience. A lot of people are trying new things out. For us, we're diving into video a bit more as a medium. I'm not entirely sure how good virtual confs are going to fair in the next year, but from what I've seen recently, I'm not optimistic about the platform.

Other roles we've seen ourselves optimizing in lately... being a more useful resource internally especially for our sales organization -- helping them craft a better story, providing better demos that are reusable, writing long form guides on the stuff you probably wouldn't have thought to write about in the past.

It's on https://www.adobe.com/summit.html

Using a DOM element is the most efficient way to do this.

There's also http://atlasboard.bitbucket.org/

I just bought an OnHub last year. WTF Google?!

Reminds me of http://atlasboard.bitbucket.org. Nice job!

I'd start at https://developer.atlassian.com/static/connect/docs/latest/i....

Looks neat for demo apps. I did try it out on one of my simpler express based apps and it failed during the npm install. Looks like this is possibly using ied?

How does this compare to azk http://www.azk.io/ ?

This lib isn't new. Glad to see it here on HN. I remember building a simple editor for it on jsbin a few years ago:

http://output.jsbin.com/ebahuh

First, use your first instinct: SURVIVAL. Do what you must to get the best insurance you can -- if that's cobra, do that (it's more expensive than a regular ppo/hmo plan as a regular employee, but also usually better). Also, doesn't Obamacare now allow you to be under your parent's plan up to 26yo? If you're getting married soon, then get on your spouses plan if it can cover your treatments -- don't be concerned with raising premiums for the startup... this is what insurance is for.

Figure this out pronto. This is your top priority! Have someone help you!!

My wife was diagnosed with metastatic breast cancer back in 2006. I worked for Oracle at the time via the acquisition of PeopleSoft. I never wanted to stay at Oracle, but I ended up staying for 6+ years just so I can stay on Oracle's United Healthcare PPO which was the best. It covered almost everything including getting multiple opinions to crazy expensive clinical trials. I finally left Oracle in 2011 and moved over to Atlassian only once I knew for sure that switching insurance plans would not affect my wife's care, but even then, I still bought Cobra for the first month into my new job just in case.

I know it sounds unheard of for many people here on HN to stay at a job you don't like just so you can keep you and your loved ones healthy and alive, but when it comes down to it, surviving is top priority.

Hi. Rich from HipChat here... the sed style replace is available in the web client now. When we released the beta it wasn't there, but we've added it back in since then.

Rich from HipChat here. I haven't looked at all the various Flux libs out there, but since Facebook's initial announcement of Flux, they've made their example a bit more generic and it can actually be used as a starting point https://github.com/facebook/flux.

The big thing with flux is the dispatcher. You don't want to get into the habit of using your dispatcher as an event emitter. Once you have a proper Flux dispatcher, the rest falls into place.

You don't need to be an admin to get an API token... https://www.hipchat.com/account/api

The new API allows you to request personal tokens or room tokens (you'll need to be a room admin for that).

What's happening with Dokku since Flynn is also going to be open source? My understanding is Flynn is based on Dokku... since Jeff Lindsay is involved.

Diff'ing images through `git diff` that results in a browser tab showing the two images side-by-side or overlayed would be cool to see.

Awesome job guys! Congrats!

(boom) It was only a matter of time. Awesome stuff. We'll definitely add this to our Stash RTE add-on (firepad based).

Now they need to introduce lower priced option for 512M.

Congrats guys! I love Firebase!

> Looks like Stash is what they sell to enterprises, versus BitBucket which is hosted. Anyone know if these are completely separate products, or if they share a common codebase?

Two separate codebases. Bitbucket is running on a Python stack (Django) and Stash is built on a Java stack (traditional Atlassian stack). Stash can be extended through plugins (https://marketplace.atlassian.com/plugins/app/stash/popular?...)

Try it again in 6 months. You won't regret it.

Stash's internals are completely extensible. Having access to the source allows you to extend and modify it to fit your needs. On top of that, you can build features (i.e., plugins) on top of Stash that you can share or sell to other Stash users on Atlassian's Marketplace.