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.
Has progress stalled? The latest generation smart watches are massively better than the last pebble. The hardware that consumers have today is borderline magic. Just because they don't throw in crazy gimmicks in to each years release doesn't mean there was no progress.
Pebble didn't get crushed by a big money monopoly.
Some people are willing to be "niche" and some people aren't. A company that produces 100 laptops per month for $100 profit each is not Apple. But that still means there is $10,000 per month left over after all salaries and other expenses. It's not a path to fame and glory, so few are interested. But it could sustain a very small company for a long time outside the world of monpolies and big money.
But if you've figured out how to produce 5 laptops per day, 20 days every month, you're in a strange space. That's not a garage operation. So why not 50 per day? Then the eternal quest for growth leads you back into the world of monopolies and big money.
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.
DDD principles are very helpful and "robust" but they address, specifically, untangling complex domains and requirements: sometimes it's the main software design challenge, but often other aspect of architecture that DDD doesn't have a lot to say about are much more difficult and/or important.
For example, from a domain driven point of view Awk operates on a simple structural hierarchy of input and output files, lines and fields; designing a nice DSL around the obvious operations on these entities is clearly a much greater achievement than designing (or rather postulating) this model.
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.
Why would remote work for a foreign company not be subject to local law and require a work visa? While few countries will care if you answer the occasional work email while on vacation, living there for months while working remote is problematic.
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.
You actually want a mirrorless camera, not a DSLR one. If you intend to only use it as a webcam, probably just buy Panasonic G7 or Canon M200 for $500.
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.
