name-needed VS lowdefy

For my long term side project I just dump ideas into a barely organised backlog.md [^1]. After finishing a feature or taking a few months away, I normally dive back in by browsing this and choosing the next milestone.

It's worked well for a couple of years, and helps me keep the long term goals in mind.

[^1] https://github.com/DomWilliams0/name-needed/blob/develop/.pl...

https://domwillia.ms

It uses a custom static site generator because I needed to procrastinate somehow before starting the first post... Now it's nicely stable and punishing new posts is quick and easy

Location: Tallinn, Estonia (UK citizen intending to move there)

Remote: Willing to work partly remote but I require a sponsored visa to work in Estonia

Willing to relocate: Yes, to Tallinn :^)

Technologies: Rust, C, Python preferably, but C++ too. I enjoy low-level work focused on performance; see my toy OS, JVM implementation and game engine on my github profile.

Résumé/CV: https://domwillia.ms | https://github.com/DomWilliams0 | please reach out via email for my résumé

Email: [email protected]

I've written some pretty low-level OpenGL bindings in Rust, because the existing solutions are either too high level or over the top complexity wise.

At the time I only had experience with the OpenGL C api and didn't want to learn a totally different Rust abstraction or mix C/C++ libraries into a pure Rust project.

https://github.com/DomWilliams0/name-needed/tree/develop/ren...

I've been alternating between two long term Rust projects, which seems to work in keeping the motivation up for both!

A Dwarf Fortress-like game (and engine): https://github.com/DomWilliams0/name-needed

A x64 operating system: https://github.com/DomWilliams0/DomeOS

A Dwarf Fortress-like game (and engine) in Rust: https://github.com/DomWilliams0/name-needed

Ambitious to be sure, but after a year and a half I'm still consistently working on it, and still enjoying it!

I'm really enjoying reading through the docs and the tutorial. We've created Lowdefy, a config web-stack which makes it really simple to build quite advanced web apps. We're writing everything in YAML, but it has it's limitations, specifically when doing config type checking and IDE extensions that go beyond just YAML.

I've been looking for a way to have typed objects in the config to do config suggestions and type checking.. PKL looks like it can do this for us. And with the JSON output we might even be able to get there with minimal effort.

Is there anyone here with some PKL experience that would be willing to answer some technical questions re the use of PKL for more advanced, nested config?

See Lowdefy:

https://lowdefy.com/

https://github.com/lowdefy/lowdefy

Awsome! With Lowdefy we tried to build a low-code framework that works like code. We’ve developed a schema in which to define applications and we’ve built all kinds of apps for enterprise customers. Massive, advanced CRM systems, call centre solutions, ticketing systems, a light MRP, all kinds of survey apps and so many dashboards. Even our docs and our website are Lowdefy apps!

Give Lowdefy a try and reach out it you have any questions or want to see what is possible :) (We need to invest a lot more into content and examples, bootstapping is a grind!)

https://github.com/lowdefy/lowdefy

Also add Lowdefy onto the list https://github.com/lowdefy/lowdefy

co-founder here :)

100% this. And yes, good documentation takes a lot of investment but it pays off like compound interest. But with that done, it becomes even more important not to pull the carpet for no good reason, you are building a tower and documentation is at the foundation.

We’ve built Lowdefy [1] as an open source project and documented it with all effort, 200 pages of docs. I often forget why or how something works and then jump to the docs. This investment keeps on paying of as we use Lowdefy to build customer apps, new devs in the team typically take less than two week to get up to speed and start making contributions, the sharp ones, just a two or three days.

This year, we’re extended our documentation onto customer apps aswell, with flow diagrams, state machine definitions, detailed field level explication schema definitions, and end user test procedures. The key here for this documentation is detail. It should be easier to reach for the docs and the the answer, than to dive in the code and interpret it.

1 - https://github.com/lowdefy/lowdefy

https://github.com/lowdefy/lowdefy Co-Founder here.

Check out https://lowdefy.com/ they even have a sample survey app as one of their examples.

You can build an app that would do this

Lowdefy is a low code tool that uses AG Grid as a block component, allowing you to create apps which render data in AG Grid without a lot of coding knowledge. There is a Lowdefy example using AG Grid here.

Shameless plug, also check out Lowdefy - https://github.com/lowdefy/lowdefy

I’m also going to jump in here and say try Lowdefy https://github.com/lowdefy/lowdefy - co-founder here.

We take a different angle and believe that low code should still work like code. We focus on a developer first approach.