02020202

Just a tip - i use tinywall firewall to prevent windows from doing anything in the background. i used the built-in firewall as well but windows has multipel services that can act as proxy for other services to avoid blocking. tinywall is simpler. i only disable it for updates, WHEN I WANT TO UPDATE. it has been working for me flawlessly. also, install windows without internet connection.

this is the modern world of monopolies and big money. they either buy you out or crush you. this is why progress is stalled these days so much in hw and sw world. it's just not worth it and requires way too much backing to succeed and be able to compete with these monopolies.

i hate vendor lock-in. hence, i will never buy apple products or anything like this.

parasitic commies killed the old host. new they need to feed off of a new one.

tl;dr but i wholeheartedly disagree. i can live without the lingo but the concepts are incredibly important. especially in large and complex projects. even though, in essence, it is all merely about encapsulation of data and actions that can be performed with/on them within context. it is good to have some general understanding of what is actually being done, conceptually. and having a philosophy with a name helps.

makes no sense. she is not working for a local company nor is being employed through local labour laws. this cannot be a reason for being kicked out of the country. they mentioned she promoted lgbt and indonesia is a muslim country so i would think it was more about that than anything else. just lazy journalism.

if there is mutex involved it will always be blocking in some way. the best way i think would be to package the client's request with response channel. loop through incoming requests and pass them to workers(goroutines) which will send the response to individual client and close said response channel. then it is merely a decision on whether to go with N workers that will process the request channel or if each request will result in its own worker via goroutine.

oh yeah, the webcams suck big time. even the expensive ones. just get a dslr over hdmi. it's 100x better and used dslr is cheap these days. you can even get panasonic gh4/5 which is a real video camera.

this is yet another issue for programmers but not for the business. the product is seen as a black box by the business and if it gets expected output for provided input, it does not matter what is going on inside of it. it makes money and in the end that is the only thing that truly matters.

of course programmers will keep on complaining but in the end, it does not matter. if it works, don't fix it. doing rewrites brings nothing to the business, only to the developers. sure, the rewrite will save dev hours along the way but the rewrite itself is not free so all in all...if it works...

btw this is also why language design of composition instead of inheritance is so important for big projects. you will learn this way way too late if you do not get it already.

cqrs is great, but you need to emit changes in your system in consumable way in order for cqrs to work since it is based on reaction to these changes and building the "views" from them. not fun to implement, a lot of code is needed, especially if you are doing event sourcing and not just some simple event logging. but it is VERY powerful design, in conjunction with event sourcing. it essentially removes strict schema from your system and you can have fluid data storage and perform various analytical tasks with past data and not being locked only to current data. very powerful! it is a dream to have but a pain to implement.

fuck recaptcha and all websites that make it impossible to use without it. the state of current things is insane. i can't even talk with the government or pay some bills without letting google spy on me. this is ridiculous.

yeah, the thing is that at the beginning you just don't know what you'll need later. so sticking to anything strict will become a limitation sooner rather than later. it is pain to do the manual work in every project over and over again but "this is the way", unfortunately.

i have done two event-sourced project in a row and i am trying to make a reusable library that i can use from now on, which will allow me to write projections so i am not tied to any schema and can build any data structures i'll need.

this is essentially cloudflare privatizing public networks and the sheep eats is like hot steaming... fudge.

jews be jewin'

lol, thanks for the downvotes. so i guess it was not that good of a read after all :D

nature doesn't need to be proven. it just is and it does not care about your feelings.

ah, well. then i guess upc, tcom, orange...they are just "shady services" ok. good to know. you've change my life.

that was a surprisingly good read

among other things, it has the fugliest syntax ever created in the history of human kind. plus laughable windows and IDE support. that's plenty for me.

ps: you can run monolith or monolith with microsevices just fine, but avoid SoA like cancer. people take soa = microservices, which is just not true. view microservices like cloud functions or cloud run, not as vps a instance.

only murica has software patents and software patents are fucking retarded.

cool thing - stripe is shit, lets make a better one.

stupid thing - write a shopping list app that will notify me when i am on my way home and near a grocery store

cool thing - lets make a database that does it all, schema is irrelevant

stupid thing - i just want a cheap theme for my wordpress blog that doesn't require me to know programming

cool thing - kafka it too complex, lets make a faster, simpler and better one

stupid thing - did i miss my bus or is it just late?

....just incredibly boring things that won't interest any programmer but ordinary people find useful.

it brings massive overhead, complexity and time investment in designing and maintaining the infrastructure and the entire build pipeline. instead of working on your business logic/product, you will spend a ton of time on cloud stuff(I wasted an ENTIRE year on this once). it will steer you into wrong direction, technologically. keep in mind that sales and PR people push cloud on you most of the time, not real devs and successful people. not to mention that it is crazy expensive + expenses cannot be precisely known in advance. it's a guessing game. bare metal is king and the argument of maintaining it yourself falls apart when you calculate some basic pricing and find out that after 4 months in cloud you get to own the hardware itself and the money yo usave can pay for multiple sysadmins if you want to.

ah, rust...the quasimodo of programming languages.

i have been dealing with this for about 15 years now.

all i can say is avoid cloud like a plague and look for stupid-simple-things. even if it does not excite you, those ideas usually work the best. don't try to outsmart people, you will fail. look for simple opportunities. and if you cannot make MVP within 3 months, forget the idea and move on.

you have essentially vendor-lock-outed yourself. people love to keep multiple things in the same place but it creates a single point of failure.

iirc google requires another email as backup address for exactly this kind of situation. don't you have one set up instead of just a phone number?

that's why mozilla rolled out dns over https.