iNeed

Submit a formal Request. Validate and Process automatically.

Visit Website
April 20, 2020 First integration between FE and BE!

Like the title says, this is the first time the front-end and back-end have been integrated together. Might not seem like much, but when building your first useful application all on your own, progress that really seems like progress, comes very slowly. This is one of those moments where it is exciting again, seeing the FE be somewhat usable and looking forward to further integrate it with the BE and finally have a beta version that I can show to people.

EDIT: I temporarily switched the BE back to TypeScript because it was faster to build. But I'm not giving up on Rust. Perhaps when scaling becomes an issue...

Here's a peek at the FE:
https://www.imgpaste.net/image/pD9Yw
https://www.imgpaste.net/image/pD0U7

Comment

March 2, 2020 Well... I switched to Rust!

TypeScript and Rust are my main 2 languages that I use and love. Since Rust got Async support officially out, I couldn't stop myself. The Backend is now written in Rust, uses warp for the web server, diesel for the ORM and works fantastically!

I also opened up a Github project with the Kanban template so I can get a better idea of what needs to be done next, since I work on this on and off unfortunately (due to day job), and it's hard to keep track.

Now I'm working on extending the domain model with more entities and adding CRUD for them as well.

I need to make sure I'm structuring the project correctly and modeling correctly as well, so I'm also quickly skimping over DDD principles and articles just to make sure I'm not doing something wrong (one day I'll finish the DDD book!). Rust is very nice and fairly easy to refactor, but I need to focus on finishing a working MVP or even getting to market as soon as possible.

OK, back to work.

PS - The front end is WIP too, built in Vue.js 2 with TS.

Comment

October 31, 2019 Finished minimum working GraphQL backend!

I finished a minimum working GraphQL backend with Typescript and type-graphql, interfacing with a SQL database (currently SQL Server)! I find that I have a better time writing backend code than frontend... but I still love good looking frontends, so I will now focus work on the frontend.

2 Comments

  1. 1

    Hey Paul,

    The links are showing a GitHub Not Found page

    1. 1

      Yes, the repository is not public. Only partners have access. In fact you are right, I might as well remove that link.

August 1, 2019 Came up with an idea for a new tool!

At the place where I work at, I'm an IT manager/director. My team frequently processes requests for new entities to be added to internal catalogs: products, partners, matches between internal and external products (from suppliers), etc.

I came up with an idea for an app to help everyone work faster and remove the dread of doing these small, repetitive and trivial tasks every day.

Instead of submitting incomplete/uncommon/unfamiliar or seldom correct data from one department (sales) to another (IT) by email and having the supporting person copy-paste and switch between apps for 20 fields that he needs to fill in, why not build digital forms, with proper validation, that the first department can fill in and submit only when filled in correctly and that then the second department can inspect and after validation/correction, with the push of a single button, immediately process that request?

Should be a simple tool to write, that lots of other businesses like ours could use in Romania, since there are a lot of businesses here that use the 3rd party application(s) we use. iNeed could also be sold to the makers of that 3rd party application we use if that's advantageous.

Comment

About

Help the different departments inside a company or companies (B2B) to process frequent, blocking requests, more easily, by automating data gathering and data input, validation and processing of formal requests.