This one came from a nonprofit. They run a community platform, a journal, and a content archive. Real work, real impact, real accountability to their funders. And you guessed it: I was exactly the right person.
Their data situation was the most common kind: functional enough to survive, broken enough to cause pain.
What looked like a reporting request turned into a full infrastructure rebuild.
Their initial ask was actually two things — which, in my experience, is already a sign someone has been thinking hard about the real problem.
They wanted:
An internal operational dashboard — interactive, real-time, for the team to use daily. The kind of thing where you notice Reddit Ads stopped performing and you move budget before the week is over.
An external board report — a static, beautifully designed PDF that arrives in someone’s inbox on the first of the month, ready to drop into a funding presentation without touching it.
Two products. Two completely different jobs. Both broken.
When we opened the hood, the actual situation was this:
→ All data entry was manual — someone exporting from WordPress, from GA4, from Google Ads, and hand-keying it into Google Sheets. Every month.
→ No historical storage — meaning you couldn’t actually show trends. You had last month and you had this month and that was it.
→ No custom engagement metric — despite engagement being the core thing their funders wanted to see evidence of.
→ No automated reporting — meaning the monthly board report was a craft project that consumed hours of someone’s time, every single cycle.
STOP capturing business logic in dashboards.
You’re shooting yourself in the foot..
Dashboards are a presentation layer.
They should presen
Dashboards are a presentation layer.
They should present the data as it is (I’ll accept very minor calculations on top).
Business logic should always reside at lower levels of the stack. Why?
Imagine this scenario:
- your CEO looks at the dashboard
- they spot a weird metric movement
- they send a question to the analytics team
- analysts run queries frantically, trying to reproduce this number, but are unable to..
This is clown town 🤡
When business logic is in the right place, it enables reusability, proper governance, and control.
Easiest way for a simple frontend for my database?
Hey,
First of all this is a great communication,yesterday I asked for help for one of ky queries and thankfully many people responded and helped me.
Anyway, I need a simple front end for my database. I created my database with PostgreSQL, I wrote my queries(around 10 of them) and now I need a simple frontend where the user will be able to give some input to my queries and the front-end will need to present the tables of the queries.
For example(let's say I have a table with students and their hobby)I have the following Query:
SELECT student_name, student_surname
FROM students_hobbies
WHERE hobby=?
The user will need to enter a hobby and the front-end will need to show a table the result of the query(the name-surname of students that have that hobby).
We(it's a uni group project for database, but the frontend part is something we need to find on our own) tried using Intellij but after hours of trying we keep getting some errors that we don't know how to fix.
Some of the programs suggested were NodeJS, (sth called Apache?)
So what is the simpest/easiest program to do what I described?
theartofmadeline
snowghoul
blakekathryn
prguitarman
pixelskylines
vaporwave
