Ataraxy

I've been messing with this using moleculer and node on a project. Feels like a good compromise.

I'm sure some HF's have, just as some HF's lost billions in their own right on the way up.

Oh I know you didn't I was just pointing out the parallel to the point being made. :) Similarly the majority of people trading options are gamblers.

Similar to calling all retail investors amateurs.

Not only that but there's plenty of people that work on wall street that no doubt hang out there all the same

That says more about the fundamental problem with the system than it does any given individual. When I see stuff like this that tries to push blame on an individual for tweeting I have to immediately scoff because it totally gives cover to the system that gives people a very healthy amount of rope to hang themselves with in the first place.

This isn't a defense of the guy by the way since all of this schtick is to ride positive PR as a billionare looking to enter political office in a climate where people aren't exactly enthused about billionares.

They realistically are. It's pure media fiction (and scapegoating) that a bunch of regular people are somehow moving markets. In practice they're just the smoke screen for the actual wealth making plays against their peers that screwed up in this scenario.

It's a character study more like Mad Men meets Forest Gump in the silicon valley nascent tech startup era.

Personally I think it's better than Mad Men.

I'm the same way.

I listen to all sorts of music and it doesn't really change much. Realistically I tune out of the lyrics while I'm focused on something else anyway.

I had began creating my own sort of thing on top of Hasura which I prefer but this is pretty cool. I'm not at all too big on TS (which is sacrelige apparently) but I'll check this out.

I tend to favor abstractions so that services can always remain agnostic. It's one thing to buy, but it's another matter to be locked into something. Especially if it's core to your business.

Considering the post is on /r/geoguesser it's much more likely they're just really good at stuff like this.

Some people are just insane at that game.

That would be Hearthstone but your point still stands.

Wow, today I learned. I remember Back Orifice back in the day was all the rage.

It's probably because so called centrists don't stand for much of anything beyond trying to gain a social edge by pretending they're above it all when they aren't. It's an excuse to attempt to distill belief systems into a very narrow point of view precisely like you've described with the whole "only reason" nonsense. I'd really appreciate it if one could describe why they consider themselves one since it's totally meaningless to me when someone self identifies as a centrist.

Just like in marketing it's all about how you frame a question to a person. Realistically most people share common beliefs at the fundamental level in what they want to see out of the power structures in our society. In other words, the vast majority of people in this country want to improve upon their material conditions. The rest of the circlejerk is just grifting.

Yeah, screw you left handed freaks! /s

The vast majority of people don't have a coherent ideology.

It legitimately comes down to however you frame a question to someone.

I'm still unclear on why a code of conduct beyond "Don't be an asshole just to be an asshole" is even needed.

On the very small boards you use chording to access different layers for symbols and numbers.

Like for me I hold down my right thumb key (which is also space if i were to just tap it) and that changes the layer allowing me type symbols like (){}[]<>.

In practice it's as if you were using shift to capitalize something and it becomes second nature very quickly.

Getting used to chording and layers is what allows you to eventually use less and less keys like the split 36 key board I use these days: https://kagizaraya.booth.pm/items/1235510

I'd make the cursor a little lighter shade in color if it's a blackboard.

Took me like 3 or 4 days to get up to my normal speed of a bit over 100wpm.

This was also going from 60% to my first split/ortho.

Took me another couple of days to get used to chording and these days I use a 36 key split board.

So your mileage may vary, but it's definitely not going to take you months typically.

I don't know even other platforms are starting to build plugin integrations into it.

For example, Google Cloud Code which lets you deploy/manage cloud run and k8s from it.

As a senior in HS it was the very first year our school had programming as a class and it was only for Turbo Pascal so I learned the basics of programming through that. It didn't really stick though (at least consciously) and a few years later I ended up self teaching myself PHP then Ruby then JS through necessity/curiosity.

The very next year they changed it to C++ and I wonder how things would have turned out differently had I been a year younger.

That's the internet and life in general. Most things tend to be personality driven unless the person is beyond exceptional over their peers in which case they have merely a larger percentage chance to break through just by virtue of skill alone, but even this is far from guaranteed.

If you had infinite memory and energy such optimizations wouldn't be needed to begin with.

So if it's a long running task that's definitely a more complex problem that would require some sort of queue/pause/resume system presumably but I imagine the same concept could still apply.

The node that merges context would simply have a requirement/dependency on the results "provided" by each branch. It would wait to execute until those requirements were met.

The user wouldn't need to know about the data model still, the "merge node" would just intrinsicly wait for the results provided form the seperate branches.

Fundamentally when each node completes the system itself just needs to check against the list of nodes to see if its dependencies have just been met and keeps track of which nodes have been already executed so that they don't end up getting triggered again when the next check happens.

There will always be a need for some sort of workflow level state or context management that governs all of this orchestration that you would want to persist to a database somewhere if this is a long running workflow but this is a systems concern and the user doesn't need to know about it.

That was just a long way of me more or less saying that it doesn't matter how many branches there are, all that matters ultimately is that a node waits to execute when its requirements are met.

The idea of a pseudo flow based programming worfklow has always appealed to me because I think having logic as components that can be used as legos makes sense. It seemed like the other stuff out there was either too overkill/obtuse or even too low level for what I had in mind. So I started writing something for personal use in JS that fits my mental model of what that would be.

In a nutshell it's just a runner and uses a project called moleculer which is a microservice framework that I'm more or less just using as an rpc client to execute the tasks of the workflow.

One thing I've been debating with myself is how I should work with the dataflow. Would you say it's better to have the results of every node merged into a singular context across an entire flow that is passed to every other node/block (ie. always one input, the context, one output the context), or would it be better to explicitly declare and pass in inputs/outputs.

Here's one project that does it that way: https://github.com/danielduarte/flowed

One benefit of this seems to be that nodes can run in parallel the moment their dependencies are met without having to care about each other.

I poked around on your site and I like what you have to offer. You appear to do it the singular context way which I suppose makes sense because it seems like every block is an individual lambda. This also seems like overkill for my purposes because I'm interested in being able to do granular things if I wish such as a simpe rule action. I'm not sure having an individual lambda to run "if email exists return true" would be practical. That and the warm up time/latency.

The other thing is managing something like npm dependencies might be annoying across blocks.

Being able to create arbitrary API endpoints is nice though.

I wish there were something a little more in between than all of these enterprisey offerings.

I've been really interested in creating my own workflow engine for personal use and I kind of had the same thought while trying to plan it out.

One approach that comes to mind to solve this sort of end user issue would be to explicitly define all inputs/outputs for the dataflow of a node as "requires" and "provides". In this manner each node would run in parallel the moment their requirements (ie. dependencies) are met. Additionally, since what each piece of data a node needs and provides is explicitly defined you could technically automatically wire nodes together without having to even really needing know the underlying data model itself.

So it just means needing to define clear unique labels for each port. In a UI a user could just drop nodes into a space which would automatically wire up to matching ports. You can then display which needs are not met and even have an interface for choosing matching nodes that fit what might be missing.

In the end all you would really need to know is how to compose the pieces of logic to get the desired outcome.

I'm a novice at this stuff though so take that with a grain of salt.

Very satisfying effect.