B3nhard

Continuously learning and Experimenting, Love every line of code 😂

Python || Golang || SEO || Angular

[B3nhard @b3nhardo]

@TechByTaraa C then C++ then any other

[B3nhard @b3nhardo]

@piyush784066 Zorin won't disappoint, it feels more like windows 11 but faster

[B3nhard @b3nhardo]

@dev_maims Deleted Antigravity, cursor and VsCode for Zed, I'm never coming back

[B3nhard @b3nhardo]

@ed_kemboi Huku already sisi watu wa wantam na wale wa tutam ni 50/50.
Ni mbaya😅

[B3nhard @b3nhardo]

@hanmanalaa @ChineseEmbKenya Basically what they are saying is that they want our raw materials with zero tarrifs and ship finished products back at a higher price😂
There's nothing africa benefits actually, its more about them than it is about Africa 😂

[B3nhard @b3nhardo]

@Angle__wix Superman will smoke the whole Team alone😅

[B3nhard @b3nhardo]

@CollinRugg They say Africa is more dangerous, yet there must be a shooting incident every week.
Make it make sense😅

[B3nhard @b3nhardo]

@Ojayy031 @AfricanHub_ Hii si kenya mkuu

[B3nhard @b3nhardo]

@_onlyscott Vitinha

[B3nhard @b3nhardo]

@tech_girl VPS always, i already have deployment pipeline setup , I just create a PR to main and thats it

[B3nhard @b3nhardo]

@fidexcode Ts/Js it doesn't matter, Ts is just a fancy word for Js with strong linter.

[B3nhard @b3nhardo]

@CodeByNZ It's understandable for web developers building websites to go with React, those building web applications and have knowledge in the three knows Angular is the god.
Angular gives you everything you need out of the box.

[B3nhard @b3nhardo]

@maigari_david @CodeByNZ Angular is the swiss-knife of everything frontend, the rest are kitchen knifes

[B3nhard @b3nhardo]

@fidexcode It depends on the size of your team.
If you use nx then you have your answer

[B3nhard @b3nhardo]

@RashedatJ Front-end has been a focus point this year

[B3nhard @b3nhardo]

@tech_girl Golang definitely

[B3nhard @b3nhardo]

Hi @elonmusk you've been verified since 1970 on X?😁
2009 would make sense.

[Hussein Nasser @hnasr]

UUIDs are 128 bit (16 bytes), you can choose to store it natively as UUID costing 16 bytes per entry. You can also store them as ascii text costing 38 bytes per entry.

You may say why do I care about storage in 2025? I'd like to switch your attention from storage and space to IO and performance.

If you index the UUID field it makes a big difference if your key is 16 or 38 bytes. Every page in the index has fixed size, we subtract the constant page header size and the header per index entry. This leaves us with precious and scarce space per page to store our keys and values.

If you have 38 bytes keys you will be storing less keys per page compared to if you have a 16 bytes keys. A single page IO (physical or logical) will give you ~double the number of UUIDs in 16 bytes compared to 38 bytes, resulting in less IOs in general, translating to more performance.

This isn’t so bad if you're doing point queries, but it matters for range and full scan queries more, especially with UUIDv7 where range queries are more relevant.

[B3nhard @b3nhardo]

@dev_TEMITAYO It is due to its compliance with ACID properties of database.
Both have their best use cases.
For a microservice architecture you can leverage both.