Excited that the Trino plugin I worked on is now live in Tabularis!
Browse catalogs, run federated queries, and stay local-first - all open source.
Thanks @tabularisdb for the shoutout
Plugin β github.com/TabularisDB/tabulβ¦
Replying to @tabularisdb
2/2 π¦ v0.1.6 is OUT NOW!
π§ Linux
π macOS
πͺ Windows
β
Requires Tabularis v0.26.0+
π Read-only for now
Another powerful addition to the growing Tabularis plugin ecosystem!
Thanks @CodeWithHarsh_
π github.com/TabularisDB/tabulβ¦
β New to Tabularis? tabularis.dev
Harsh retweeted
Best auth solution for startups?
1) Clerk
2) Firebase Auth
3) Supabase
4) Custom auth (π)
Replying to @utsxvrai @neondatabase
It happens sometimes, but after a while it starts working again.
Harsh retweeted
Replying to @arushiitwt
people who paste their daily lc solution in a github repo and make a commit for the heatmap π€‘
Harsh retweeted
Ek hi to kaam tha college ke paas ki foundation subject pdha do, vo b na ho rha inse.
Networking, OS ye to krwa dete, baaki to chalo students b expect nhi krte ab.
Tum bs NOC dene me nkhre kro n attendance ka jaap kro. Na fest krwane ka fund dete, upr se attendance me relaxation b nhi dete.
Ab koi mere paas koi benefit of doubt nhi bacha inke liye.
Harsh retweeted
I am grinding DSA and DEV so hard day and night, but it feels waste of time.
Once a legend said "26 me toh duniya khatam hai" πππππ
Agree
Just hired my first developer without asking a single DSA question
No formal interview, no "reverse this binary tree" nonsense.
Just said: "Here's 7 days, paid probation. Build this real client feature. If it's good, you're hired. If not, no hard feelings."
He's still with us 8 months later helping scale to $60k revenue.
Sometimes the best hiring process is just... letting people prove they can actually do the job.
DSA questions don't build apps. People do. π€
Harsh retweeted
Just hired my first developer without asking a single DSA question
No formal interview, no "reverse this binary tree" nonsense.
Just said: "Here's 7 days, paid probation. Build this real client feature. If it's good, you're hired. If not, no hard feelings."
He's still with us 8 months later helping scale to $60k revenue.
Sometimes the best hiring process is just... letting people prove they can actually do the job.
DSA questions don't build apps. People do. π€
Spent hours debugging why my API wasnβt workingβ¦ turns out I used A instead of a in one place.
One letter. Whole API gone.
π Built an AI-powered feedback workflow!
βοΈ On form submission β AI Agent (Gemini) interprets input
π Switch auto-sorts: Complaint π Feature request
π Logs in Airtable
π Sends alerts to Slack
π§ Notifies via Email
No more manual triage. β‘ #n8n #AI #Automation
Harsh retweeted
HOW TO STRUCTURE YOUR BACKEND CODE IN EXPRESS JS (with detailed folder explanations)
π
βββ π app.js
βββ π bin
βββ π config
βββ π controllers
β βββ π customer.js
β βββ π product.js
β βββ ...
βββ π middleware
β βββ π auth.js
β βββ π logger.js
β βββ ...
βββ π models
β βββ π customer.js
β βββ π Product.js
β βββ ...
βββ π routes
β βββ π api.js
β βββ π auth.js
β βββ ...
βββ π public
β βββ π css
β βββ π js
β βββ π images
β βββ ...
βββ π views
β βββ π index.ejs
β βββ π product.ejs
β βββ ...
βββ π tests
β βββ π unit
β βββ π integration
β βββ π e2e
β βββ ...
βββ π utils
β βββ π validation.js
β βββ π helpers.js
β βββ ...
βββ π node_modules
app.js : It's like the control center of your web application. It's where you set up and manage everything.
bin : Think of this as a place for starting your web server. It's where you have scripts that make your website work.
config : These are like settings for your website, such as where your database is or how your website should behave.
controllers : This is where you put the brains of your website explains the name controllers. Each file here handles a different part of your site, like customer stuff or product stuff.
middleware : Imagine these as helpers that help your website do things like checking if you're logged in or keeping a record of what people do on your site.
models : This is where you describe what your data looks like. If your website is a store, this is where you say what a product is or what a customer is.
routes : These are like the paths to different parts of the website. If the website is a city, these are the streets and highways.
public : Think of this as your storage room for things everyone can see, like images, styles, and scripts.
views : If your website is like a book, these are the pages. This is where you put together what people see on the screen.
tests : These are like exams for your website to make sure it works correctly. You create different kinds of tests to check different parts of your site.
utils : These are like handy tools you use to make your website better, like checking if someone's email is valid or formatting dates nicely.
node_modules : This is like your toolbox filled with tools (libraries and code) that you use to build your website. It's automatically filled with things your project needs.
Alright. that's a wrap. Follow me @mysticwillz for more tips like this.ππ
Harsh retweeted
Postgres at this point is a super power. But the biggest myth is that I know sql that means I know postgres. No my friend, Postgres at this point is like a juggernaut. It deserves a stand alone course on its own.
But it will never be a profitable one.
Harsh retweeted
Big platforms like Amazon or Myntra donβt use fancy 3D animations and thereβs a reason. When youβre serving millions across devices and networks, performance > aesthetics. 3D looks great, but itβs heavy. Simplicity scales. Thatβs how enterprise wins. BUT hereβs the flip sideπ
Replying to @Coder_kartik @AyushYadav2428
Node , Express , Mongodb















