gary__

What do people use for self service embedded analytics in SaaS applications?

As well as a reminder for those not good at staying on task, it sounds worth considering for those who spend their day satisfying constant small ad hoc requests who later get asked "What have you been doing all day?"

Hopefully it has a "same as last time" button, I doubt this has the same cognitive distraction level as fielding a question from a colleague as well. I.e. understand their question, think of the context, etc etc

I think there's often a leeway given to the full stack dev that they have strengths and limitations. I haven't got to the point where I could compete with the true / good front end dev with my skills.

Even at the backend you have the application backend (c# or whatever) and then sql/rdbms. If you are that good perhaps you deserve thrice the pay by this logic ;).

Jokes aside, at the last good company I worked for where I knew other people's pay, I was compensated for the entirety of my skills compared to the good front end dev. We earned the same, and I was quite happy with that.

Jack of all trades...

This is great.

I would prefer that browser compatability is mentioned, for my own purposes that would be IE11.

Perhaps set a baseline of what browsers are considered in the intro and then highlight deviance as it occurs.

Bear in mind the tutorial is prefixed "Relearn..."

Though I'd class myself as a "full stack developer" css for a long time was the 2nd class citizen, with most of my time spent on learning to use front end frameworks in their idiomatic way, the "it depends" peculiarities of SQL and RDBMSs and making inroads on the vast tomb that represents architectuliary sound back ends.

So an article focussed on improving my "it's only css but it works" knowledge is one of the best things I've seen on HN in quite some time :)

This could put off anyone who thinks they could be acquired by such companies from using your software as well. How can anyone know who is going to make it onto the blacklist for the next version etc. Seems quite the can of worms.

I'm building a similar editor for an app, adding [1] at this very moment for pan and zoom, this is nice work.

[1] https://github.com/anvaka/panzoom

Funny, so many people say that competitors don't matter. What size was your market?

Submit this as a Show HN, will show in the Show HN tab as well.

"At some point, I bet someone in a design meeting said "Hey, I think this might compromise security, can we study that before implementing it?" And the decision to implement it without that study, or despite it, was made."

Because we should assume all your past missteps were due to willful negligence? Yeah, let's not just start making shit up to support the group think outrage.

Not so much being a bad participant, but something I've found are developers who propose a solution to a problem outside of a meeting, but when it's then thrown out to the group for suggestions they remain quiet. Hard to know what advice to give for building confidence.

Might want to try here too https://patents.stackexchange.com/

Is it open source / online?

Reminds me of this editor project from Kent Beck for working with the AST instead of with text alone when developing, somewhat related

https://www.facebook.com/notes/kent-beck/prune-a-code-editor...

Research paper: https://www.microsoft.com/en-us/research/wp-content/uploads/...

Reminisent of language workbenches like MPS in a way

https://www.jetbrains.com/mps/

In our defemse, we also had to click a button, who really isn't learning from their time in the modern world! /S

"First off, we're huge fans of both Meteor and Asana. I spoke with Geoff @ Meteor a couple years ago when we were first starting to build out the Airtable product and was very impressed by their approach and vision. We've closely followed the developer blogs of both those projects (and in Meteor's case, their source code). With those learnings, we built our own realtime database engine that supports relational data (which Meteor doesn't yet support) and also some other major features like the ability to undo any user action out of order (like git revert), which is necessary to support undo in a multi-user context (because the last thing that you did may not be the last change globally if other people are concurrently making changes). Undo is a particularly challenging feature to implement in a structured relational database context, because it can't be reduced to a set of simplistic character insertion operations as is the case for a google word doc, or a spreadsheet (which is a simple 2d array of values without type constraints, foreign key relations, etc)."

https://news.ycombinator.com/item?id=8374468

Their Show HN in 2014, some interesting tidbits about the design. https://news.ycombinator.com/item?id=8373914