So the guy across me at work goes KLATIKY KLAK in the keyboard n i always wondered why

coz we're mid/senior devs, there isnt that much to type usually

saw his screen a bit ago n the nigga typing/copying code from ChatGPT 😩

Happy Diwali people 😤

Ive to work on my should've-been-a-day-off coz big meeting so y'all better celebrate in my stead 😤😤😤

In the saga of the unnamed SAAS I've talked about before, LOOK AT THEM USER-SESSIONS XD
And this is only from Android-App embeds since web-embed isnt even open to public yet, so no google-crawller false-positives

The country I'm in, has only 8 sessions waayyyy down below so my code isn't messing up the numbers :3

I'm still too much of a bitch to face this product head-on and "launch" it damn this feels good 😤🤘

New internet 🥵 Imma stream 8K 3D porn now

A TypeScript boolean/undefined Flag variable kept fucking up
true == true didnt hold true

checked the "typeof" in console and it's GOODDAMN STRING.
What's the point of TypeScript's "type safety" if a Boolean variable is holding a String type for whatever reason. URGHH I HATE JAVASCRIPT.

So given how easy and flexible UI-making is with JS frameworks for Native Apps in Android etc, how long is it before they sideline Native SDKs in favour of WebAssembly-based native 'apps' the way UWP/WinUI is on its deathbed?

it's sad but i honestly envy the ease of native webapps, specially rn while making a Java Android SDK

A new subsea internet cable between the country I'm in and where my server is, went live a few weeks ago

The rsync from local PC -> remote server went up from avg 500kb/s to 4mb/s

the subsea cable website says they're aiming Nov/Dec launch so it's probably in semi-live stage rn but still cool 🫡

VK has the weirdest client side errors 💀

I made a SMALLLL change in a .NET middleware that handles WebSockets (in the self-made SAAS I previously talked about) and it somehow fucked up n stopped closing connections even for people who left

On the bright side, I didn't notice any performance reduction in the service so the scalability was unintentionally stress-tested lol
Now to figure out how it fucked up

I made a Product in my free time (after work hours)

it's a SAAS thats supposed to be an add-on to apps and websites

Added it to my own apps (what better than Test in prod) and over months fixed its pitfalls n ngl, even im impressed by its core tech and resilience

But thats kinda it -.- Ik I should make a landing page and launch it etc but I lost the will the day the "core tech" was 99% perfected
Im a Product guy not a businessman T__T

It's the weirdest mental block ive had in a while ffs.

For someone not deep-into-security, can someone tell me why "encrypted"/"non-compromised" communication is hard?

Wouldn't a private server that holds conversation in-memory (imagine Dictionary holding U2U GUID-GUID list of 'msg' objs) suffice?
Incoming IP info is disregarded and nothing gets written on-disk ever

Need to erase everything? just reboot the server, it's all in memory anyway

To avoid man-in-the-middle, pre-handshake check cert integrity by exposing the certificate-fingerprint by another endpoint, if the fingerprints match, proceed to switch to websocket
Wouldn't this be wayyyy more secure for actual anti-establishment talks than all the fancy probably-backdoored software that exists today? .-.

Hell it's easy enough that someone could make it go live in a few days, keep it up accessible if you know the IP and port to communicate and close-and-delete when done

So I thought of applying for masters, mainly coz work's been boring af -_- i'm not having Fun. like. at all.

Masters in CS would need a research topic and the one I was/am interested in is "WebRTC", with the topic being tryyyying to figure out a way to hide the actual Peer IPs and come up with a Standard 2.0 of WebRTC or a derivative standard

I was looking into Research Papers already written on WebRTC to get a feel on what's already been attempted or tried
And omfg the word-vomit :v

The whole paper had 0 substance and their "research" was that "we'll encrypt Packets with SHA256 so it'll be secure" like bruh -_-

Did anyone here ever use Alibaba Cloud? How reliable is it? .-.

I was divided between Yandex Cloud and Alibaba Cloud but Yandex doesnt support payment from my side of the world -_- so Alibaba is the last resort :v

if it's super bad though then I might as well buy another server-rack in a DC but imma keep that as the "worst case scenario"

Does anyone else here have coding-fatigue?
Like if someone gives me a problem (BIG or small), I can chalk out an architecture or "oh you can use this-n-this-n-this"

But if you ask me to code it, though it's easy as fuck, I dont want to and will drag it until I gush 2 coffees to force myself to do it.
You give me a junior dev who knows NOTHING and does the typing and I can guide him and make him do it all, but by myself? nah

PS: this only applies to work-code that isnt "fun" per-se. My own projects? no issues at all

My dumbass fucked up a good interview by looking down on the company I was interviewing for unintentionally (:
They outsourced the "core" finance code to a 3rd party B2B provider and I was like "oooooooooh so y'all are only a wrapper? That explains why you didnt do super-crazy background check on me hahaha"

I ended up sounding suspicious af :'v

work-vibing 💪😤 https://youtube.com/watch/...

I was all hyped up coz I WHINED AND BITCHED FOR MONTHS against a 5-6y old B2B company offering, that it's shit n needs to be remade

And they agreed, n only 2 people assigned to it yet, the last chief architect and me

But last guy is old n is the one who made it shit in the first place (we use Windows Tasks in a Windows Server, triggering once every minute to pretend background tasks)

n he doesnt even want 2 branches (: And is still making the same mistakes that made the last implementation shit n it's hard to stop him coz he senior and old

And now I kinda dont care, but have to coz job market's shit
Ffs

Visual Studio's intellisence recommending me NOT to use

ISomeService = new Service() and just Service coz the latter is faster (these are non-DI services)

is giving me a wierd anxiety. I'd prefer to stick to exposing Interfaces just as a convention but the constant💡is killing me :v
//I know the actual performance difference is neglible, but retarded mind still focuses on it even if I dont want it to

did every social media adopt a common AI/ML algo for timeline recommendation or what.

EVERY goddamn platform now recommends posts heavily biased towards the last 5-10 accounts/topics you've interacted with.

I have to manually go delete my history/"saved data" just to get a fresh air of posts every few months.

I miss bit-flags 😪

Has anyone here had a need to use Unmanaged Code, ie C++ interop for the sake of performance on a practical level? (ie, not just coz it's fun)

Im excluding driver or OS level code.
Only Server Side OR User side programs

Coz wouldnt the overhead of talking to unmanaged code overwrite any CPU-time benefits?

Ain't no way 💀💀💀

I spent a whole day trying to debug why the backend would stop sending data after a while (-> it filled up its connection pool)
but after I turned pooling off, there were a number of dangling Client-Idle-Read DB connections
//not using Entity Framework in these N services, it's pure SQL and DB-AccessLayer here

Never happened before, looked up conf, looked up SO
Changed connectionClose to mandatory Dispose
Still didnt work.

long story short. Turns out in 1 of the services, the DataReader to POCO static method, was disposing/closing the READER and not the CONNECTION.

I sent it as tuple instead of 2 separate variables (reader, connection), and the Item1, Item2 got mixed up (:

Totally my fault, and imma avoid name-less tuples from now on like they a plague -.- thats my 2024-resolution

facebook for iOS rn (:

AI is tech industry's fidget spinner
Cant wait to see it go out of fashion.

😩😩😩

Im creating a "settings" functionality of sorts, unique per "account"

Ideally I'd create a new table, FK it with the Accs table with each Setting variable being a column

But im also inclined to just turn it into a JSON and not bother with N columns for it specially since arrays are involved in the settings

Could version it to ensure that if Settings change on code-level, old accs with old settings dont get fucked up

Now this is a pet project so im free to experiment, not bound by high level design documents

What do y'all prefer/recommend? JSON<->Settings Obj or plain old Table/column with FKs

Im trying my BEST to not be judgemental about my boss but damn the code's shit

It's written how a 1st year UGrad would, trying to add as many complicated shits to it as they can to show "see? I know this obscure way of writing code, cool eh"
Like they're ticking off a rubrics

There is no design language, barely any structure. MVC's Controllers go beyond 2.5k lines.
Everything is an Interface but with such horribly designed code, they just add on to the clutter

Oh and it somehow also uses ReactJS inside .cshtml, which was already out of fashion A DECADE AGO.

I was all gung-ho about migrating a .NET Framework 4.x 16-projects-in-1-solution 100+ table 300+ Standard Procedures "project" to a more streamlined Services based architecture with documentation and all

Until I realised the guy who's heading it, has been working on it since 2019-2020

And has kept his job because it's such a mess and no one else knows nor cares about how to navigate through it (:

How do y'all approach media-endpoints?
Specially publicly accessible user-uploaded media

Rn I encrypt the path to the media-
/file and expose it, decrypt on the server (returning a relative file-path) which then fetches the file via File.Read and returns it as-is

I put a cache header and works fine

But something in the back of my mind makes me feel it isnt right

Like, normal endpoints and file-read endpoints shouldnt be in the same backend, potentially affecting each other

But since it's just a fun pet project so Im not paying for a 2nd baremetal server as a CDN/media server -.-

Worst case scenario I use it as-is, but would appreciate hearing other approaches