You seem to have missed the key step. Talk to customers before you build. Build what they need. Then have them talk to you to adjust things until you really nailed down the product that solves their needs, and then have them talk to their friends about how much you rock.
Again, you need to question the premise. Perhaps all the sales and hype you heard simply wasn't true?
In reality, many organizations have already implemented the AI-based improvements to their systems that they need. That work is done, people are enjoying it. The AI vendors want to take it farther. Some coders want to take it farther. Some leaders are pushing it due to FOMO. But "the masses" do not want more. Step outside of the tech silos, and you'll find that most people do not want more AI than we already have.
Makes total sense. Consumer UX relies on pure determinism. When I click "Save", I know exactly what's going to happen. When I type a prompt into an "AI agent", I'm basically playing roulette every single time. Until we figure out how to wrap these probabilistic models inside rigid, predictable UX patterns, the mainstream crowd is going to keep treating AI like an annoying toy instead of an actual tool
It sounds like you re-invented sendgrid, but are charging more money for it.
Did you do competitive research, and can you articulate what you do that is different than the other mail platforms, and why that justifies the higher pricing?
OP was just asking for help to learn the skills, dude. They weren't saying they expected to start having solo shows in prestigious galleries or anything.
That is what I mean,
If you think learning “skills” to make visual art for CG, is just learning software or a particular “tech” or “technique”, you cannot make it work in the world of AI…
If you just want to make random stuff, just use AI.
What I was saying is that the skill of visual art including good pixel art, comes from exposure and learning visual vocab and grammar.
Sorry for the previous long winded post (habit from teaching design and CG in Ivy)
Nah, I gotta disagree. When I was studying art, getting my degree, etc., there was absolutely a line drawn between the academic pursuit of art, which did include the academic context, history, and all that rot of which you speak vs. the daily practice of art, which could literally be flinging paint around a studio and seeing what sticks. Our coursework and discussions explored that full spectrum. There were times to be academic snobs about art, and times to just let the work fly. And while you are correct that some great art comes from the middle ground where you bring context into your whimsy... trying to push that as the only place from which art can originate is simply gatekeeping.
Now, if you wanted to share your experience, and offer it as a potential path to add additional skills into OPs practice, then it could come off as helpful: "Hey, I teach design, and have found that studying x, y, z can bring you some additional knowledge that will help..." is a far more open way to express the same idea.
I am riding this tech into the ground and have been working since 2008, off and on, to shut down anyone who is using it and migrate them to modern platforms. And still getting contracts to do so! I have done your standard modern SaaS gigs as well, but these days I'm finding shutdown efforts of legacy tech is enjoyable work, while playing the startup/SaaS game is not.
It is equally important as the other low code solutions that have been floating around since the 80s. AI doesn't change the big picture, which is that when you empower non-technical people to create apps, they will do so. 9 out of 10 won't work well. Of the 10% that do, 9 out of 10 will be over-fit to the team that built it and not grow, even while solving a problem for that team. For the 1% that work, are broadly useful, and grow... they will fail at scale, and a professional team will then need to come in and smooth out the rough edges.
AI is a new tool to walk that same path. Maybe it will let people go father before needing help, maybe not. But if you are trying to run a low code platform, your focus should be at least partially on that last step of the path - how do you help people take their work farther before needing to call for help?
Fun - I wrote something similar with static HTML and vanilla JS many years ago - but it is always cool to see people bringing their own flavor to these kinds of projects.
reply