Project management is one of the use cases we plan on excelling at Proma.ai

We are launching in 2 weeks.

I would love give a demo to anyone interested. Email is in profile.

Shameless Plug: I am building Proma.ai and one of the use cases we are pursuing is trucking freight operations management. I would love to chat with others in this space - both builders and buyers.

We are working on this exact thing, would love to give you a demo and early access. My email is in profile.

My son, around the same age, liked p5.js the most out of several things I introduced him to

This looks great and would be great for certain use case like a website for kids.

And for prototyping, which I suppose is its primary use case

Not a whole lot based on our experience few months ago.

May I ask about your (and eunoia's) use case(s)?

Coincidentally, 2 hours ago I submitted Molecule.dev right here to HN (an hour before this AWS submission), a full-stack solution which aims to address all of the time consuming pain points of building (common functionality), maintaining, and releasing cross-platform apps.

It isn't a UI builder like AWS Amplify Studio, but I think we can do it better. We cover all of the most common use cases and are planning on adding more, all without any vendor lock-in or unnecessary convoluted abstractions.

That looks interesting; will give it a go in the weekend.

Whoa. Do you have an examples of anything built with it?

Next to our FAQ section (or beneath it if you're on mobile), there are links to a demo app for every platform so you can try out all the functionality currently available. We'll be adding new options every week, depending on the input we get.

We'll also soon be rereleasing an email app using the Ionic option.

I have a historical perspective on this topic. Data Science popularity was rapidly growing and "R" was the lingua franca around 2010 - 2014.

I attended Strata conference in 2014 and after visiting various technology exhibition booths there, I saw a common theme: tech companies were building data solutions using Python as R was no good for the purpose

In a meeting scheduled to share my take-aways from the conference, I predicted "Python will emerge to be the language of DataScience in few years"

Talking about dark patterns, the email was sent after 5:00pm on a Friday before the long week-end.

Triplebyte team knew that their users were not going to like it and did their best to slip this through.

Triplebyte went from being a respectable company helping skilled hackers by-pass white-board interviews to being a prime example of unethical tech company in one stroke.

They've been sketchy since inception. I was in a very early batch, if not the first, in 2015.

Remember that the premise was that they were non-adversarial, anti-gotcha interviews, whiteboards, nit-picky algo implementations from memory, etc. They purported to do some qualitative analysis instead.

We schedule a session and I get the confirmation: "This is a chance for you to go into more depth, and show us something that you've built. This will not be a high-pressure interview." I get at email the day before our scheduled session that says, "Remember that we're going to talk to you about a project that you've worked on," as agreed.

The following day, just a few hours before our appointment, a founder emails me saying, "Just wanted to give you a quick heads up that rather than walking through a project today, you'll be doing some programming together with an engineer."

They duped me into an adversarial interview. That kinda thing grinds my gears, but I went along with it anyway. I get the response: "We really enjoyed it and thought you did great. We'd love to talk more with you and invite you to a second technical interview."

I opted out as this continued. They acknowledged that they were changing things around without telling people, but it was just so antithetical to the mission that it became disingenuous.

When you pair that attitude of disregard with fact that they're playing sociologists, it's a bad look.

I disagree that nothing one could have done beforehand could fix that. The argument is not that there would not be a decline in share prices at all but the magnitude of it.

You need to have enough saved to survive 6 months w/o income is preached a lot in personal finance and somehow this is not practiced for businesses.It is understandable that cash-strapped startups can't afford to do this but the companies buying back shares to increase their stock price certainly could.

Massive publicly traded companies are not the companies that are collapsing. It's mostly small business that aren't publicly traded let alone doing buybacks.

But somehow, when all is said and done, companies like Boeing will not even face any consequence for their bad decisions.

When times are good, these companies divvy up the profits to give large bonuses.

When times are bad, they divvy up the bailout money to give smaller bonuses.

It certainly seems like there is no connection between compensation and performance once you are too big to fail.

And there is a very convenient "heads I win, tails you lose" structure in favor of the large companies.

This is an article about small businesses, which make up the backbone of the economy. It makes 0 financial sense to save up 6 months of savings for any company, big or small. This is literally a once-a-century event.

Doesn't mean it will be a century until the next one. There are other reasons to require business to have emergency funds... Weather comes to mind

Love the product concept and the problem / solution descriptions. I am not your typical customer though as I was already aware of the limitations of existing solutions.

I just signed up for this and set it up in our website. I have a couple of questions: - Is the analytics realtime or does it take time to process events? - Is there minimum data threshold that is needed before anything shows up in the dashboard?

Currently the views are generated once per hour. Everything in Volument is based on aggregation, ie we look how much "traction" is generated in the first 1, 3, 7, 14, or 30 days (based on your ability to retain visitors). All that important information is not real-time.

We see the importance of real-time tracking on the initial onboarding phase so that it's easier to debug things and see the potential setup errors.

We're just getting started so not everything in place yet.

Thank you!