Poefke

Joined 9 years ago

Karma
90
Submissions
23
Member since
Nov 15
Founder of Muze.nl and co-founder of SimplyEdit.io.

I started working on the web in 1994 when I co-founded the Student Network Twente, on the University of Twente, managing a revolutionary high speed (10Mbps) network on the university campus.

Since 1997 I've worked professionally on building enterprise web content management solutions, including Ariadne CMS and Vedor. In 2015 we launched SimplyEdit, a true drag and drop user interface for the read-write web. Today we are working on extending this to a universal low-code application builder.

View on Hacker News

Recent submissions

Comment · 3 days ago
AI doomers focus on safety and alignment, but what about our own agency, and morality?
Comment · 1 month ago
AI changes the rules of software development. This article is how I am adapting my work now.
Comment · 1 month ago
There will be no red-eyed metal skeletons marching over a field of human skulls. No machine intelligence will announce that it has become self-aware and decided to remove us from the equation.

The system most likely to take control of your life will not threaten you.

It will offer to help.

Comment · 1 month ago
Comment · 2 years ago
LINQ is much more sophisticated, translating as much of the query as possible to the target (server) language, like SQL. JAQT is not doing that. lodash, underscore, and others, had a great impact on javascript by introducing lots of functional paradigms. Most of that is now part of javascript itself. JAQT's main purpose is to allow you to filter arrays of objects and create custom objects, just like GraphQL. And be a bit easier to learn than Array.map/reduce/filter.
Comment · 2 years ago
Author here, if you are comfortable with filter/map/reduce, than JAQT doesn't provide much benefits, I agree. My target audience is developers who aren't that used to that. I've had much more success with junior developers using JAQT, then trying to get them to use map/reduce.
Comment · 2 years ago
The target audience for unit tests is not the client, it is the developer. Unit tests allow you to change code with more confidence. 100% code coverage is not a useful aim, you should aim for 100% confidence in your code. Unit tests can also function as example code, that can't get out of date, since then the tests will fail.

Testing for quality assurance is a different thing, usually called acceptance testing and sometimes including regression testing. One easy way to make clients angry is by re-introducing bugs that were fixed in earlier releases.

Comment · 5 years ago
Yup, it was an experiment. There is a follow up, called cobalt: https://github.com/poef/cobalt/

But its not meant as production ready code, instead I'm exploring the concept and what it means for editing, rendering, etc.

Comment · 5 years ago
Hi, original author here, I just found out my old project featured here and love the thoughtful responses. If you are interested, I've been working on a new version of and on, called cobalt (https://github.com/poef/cobalt/). Hope was the proof of concept, cobalt is a more rigorous implementation. Specifically the range algebra is complete there.

It's still a hobby research project. There's a lot I've learned building and using it, about the things that HTML is good at, and what it isn't good at.

What I'm trying these days is to see if I can get a WYSIWYG editor with a user experience that comes close to the user experience of writing markdown. This isn't easy and its interesting to explore what makes that so.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton