Code and Thought
Kanalga Telegram’da o‘tish
Software Engineer | Builder | Founder | Odoo | Business | Thinker portfolio - https://neziraworkuu.vercel.app/
Ko'proq ko'rsatishMamlakat belgilanmaganToif belgilanmagan
409
Obunachilar
-124 soatlar
+57 kun
+2030 kun
Postlar arxiv
Repost from N/a
Omnispot is out: a 1-click mobile hotspot plugin for the Omarchy top bar.
Share your connection over Wi-Fi , monitor connected devices in real time, and toggle it straight from the bar.
Install:
omarchy plugin add https://github.com/NWGKGIT/omnispot.git --enable
GitHub: https://github.com/NWGKGIT/omnispotIf you want to understand PostgreSQL and Express, I really recommend taking on this challenge. I think it's more valuable than watching endless tutorials or building a bunch of mini projects.
But there's one thing I want to point out.
At the 100-million-row mark, my PostgreSQL database occupied approximately 20 GB of disk space. And Omarchy was particularly useful for this project because it gave me a Linux-native, terminal-focused development environment.
So, if you're using Windows or working with a PC that has limited free storage, you might face some challenges on the hardware side.
Just something to consider before jumping in.
So... when I was starting my programming journey, one of the most intimidating things was asking other developers for help or understanding them in general.
Everything sounded so technical, and sometimes I felt like I needed a certain level of experience just to have a conversation with them. And someone said “Be the senior you wished you had when you were a junior.”
And that's why my notes are always so long, filled with examples, detailed explanations, and things that might seem too obvious or even silly to someone experienced.
But yeah... I know what it's like to be on the other side, trying to understand something everyone else seems to already know.🥸
@codeandthought
Imagine building an application that records everything users do. Someone signs in. Someone clicks a button. Someone completes a purchase. Someone opens a page. Each action produces an event.
For a small application, storing these events is relatively straightforward. But what happens when the application grows and accumulates millions of records?
Will searching become slower? Will the database consume too much storage? Can I still retrieve information quickly? What happens when I need to insert millions of new records?
Okay, I have documented every detail on how I built this in a way that not only you but also your high school graduate Grammy can understand. So, if you wanted to take a look, here is:
[Doc]
[github Repo]
@codeandthought
Do you know the 80/20 rule?
Yeah, most of the 80% of things are in the hands of the 20%. Sometimes I feel like this narrows down to 98% or 99% versus 2% or 1%, like intelligence, creativity, and everything of this person; he is 1 in 8B.
Who do you think will be the next Elon Musk in our community?
@codeandthought
Who else thinks this is AI-generated?
https://x.com/Tesla/status/2110913438293647789/video/1
إِنَّ اللَّهَ وَمَلائِكَتَهُ يُصَلُّونَ عَلَى
النَّبِيِّ يَا أَيُّهَا الَّذِينَ آمَنُوا صَلُّوا
عَلَيْهِ وَسَلِّمُوا تَسْلِيمًا
اللهم صلِّ وسلم على سيدنا محمد وعلى آله ..💚💚
me torturing my PC by trying to insert 20M database rows at this time of the night😈
Have you ever checked these vulnerabilities, guys?
I didn't care about it before, but I asked GPT about it today, and its response was like🤨😒😔eskahun atakim?🤢
3 Ways to Insert Data into PostgreSQL: Sequential, Batch, and COPY
Imagine inserting 1 million rows into your database. You have three strategies:
1. Sequential INSERT: One row at a time
Executes a separate INSERT for each row.
Simple, but slow due to repeated database communication.
2. Batch INSERT: Multiple rows at once
Groups many rows into a single INSERT statement.
1M rows with batches of 1,000 = 1,000 INSERT statements.
Faster because it reduces database round trips and statement overhead.
3. COPY: Bulk data loading
PostgreSQL's optimized mechanism for loading large datasets.
Streams data directly into the database without individual INSERT statements.
Usually the fastest option for massive data ingestion.
One important distinction: server-side
COPY FROM reads a file accessible to the PostgreSQL server. \copy in psql reads a client-side file, and COPY FROM STDIN lets applications stream data.
How do we compare them?
Measure their throughput:
Throughput = Total rows inserted / Time (seconds)My unpopular opinion
In a startup, hackathon, or whatever, if you have to think about how your product is unique, it's not unique at all.
@codeandthought
Btw, this is proof that GPT doesn't know me better than a random stranger who spends two days with me...and i was thinking am handing over to much of my information... kinda disappointed also happy
