Microservices and monoliths have never been about cog load. Its an implementatiom detail that solves scaling, deployment and team managment problems.
The cog load should be fairly similar weather you jave micro or monolith.
There are good and bad abstractions but in the end the cog load is a sum of the leaves and this never changes in the tree. In fact the cog load is better with bad abstraction , or no abstraction.
Hard coding is no cog load. Its in that file that function for that feature.
Some engineers think that whiteboarding is not clear enough ... that code snipts are better.
The key about whiteboarding is it take away all the specific syntax and gets to the heart of the understanding the logic.
Thats what collaberation is for, i think many young engineers that only code with an ide are nervious whrn they dont have autocomplete available and they lose focus on the core logic.
Programmerd used to write on paper ... this entire process (coding without the ide/search engine) is lost.
But this is the part where the programmer shoes their strength in logic ... not syntax memory.
The point is you dont have business data yet, you need to create it ... using business logic. All the data is in sql but for some reason you dont store value x (probably an aggregate of sorts) and sql environment doesnt have a good generalized syntax for logic.
I think the problem is maintenance instead of performance. When you really want performance (in data reads) youll be precomputing and storing the values. Then your report can filter and be indexed properly.
I dont think that any tech solution will give you fast reads and fast writes you need to pick one.
Your server probably has alot of down time ... use it , make a cron job and make a seperate reporting table ... reporting on raw data does not scale , window functions do not scale
Using window functions is equivalent to using a better cpu. Maybe the environment you work in is faster but you have not factored the logic to make the best use of the resources.
You can take a crap approach in java and port it to sql. But the approach is crap and you should create a seperate reporting process or at least use hadoop.
So you like being lazy ... a technical challenge comes your way and you hope others fix it for you.
This is the hipster frontend engineer attitude. Not to be mistakened for real frontend engineers who create robust sites for paying customers. Enjoy your world and ill enjoy the enterprise dollars. I like coding. I dont complain about the challenge.
For all you know, they build websites or applications that don't have any need to run on older browsers, or at the very least, there are diminishing returns.
There's always an opportunity cost. While you're building support for older browsers, they could be adding valuable functionality to their software.
He destroyed his mind and got paid well for it. There are many dangerous jobs out there and usually the pay reflects it. The player union and company needs to invest in solutions. If there are none apparent it might cost less to up salaries then invest in R and D. The owners dont want players to get long term damage. Mining orgs dont want miners to get black lung.
Tech solutions are a great place for this but its not a moral issue. He chose to play pro football. Its not footballs fault. And not every player gets brain damage so lets hear some numbers on that. What was this guys diet? Some people get brain damage that dont play football.
Why would you think player pay has anything to do with risk of injury? There are very few occupations where this is true, and celebrity sports are close to the last place to assume that is happening.
Its not a whitelist of domains, but of applications allowed to use the agent. Right now Blizzard is blacklisting only the browsers from using it, but that still leaves a bunch of other things like slack and whatnot.
Its indeed a very strange patch from Blizzard. As if they hastily assigned an intern to it and then called it a day.
A blacklist won't allow items that match and a whitelist only allows items that match. Blacklists include by default and whitelists exclude by default.
Since the regex needs to match to be included - it is, by definition, a whitelist. It excludes by default anything that doesn't match. It just so happens the net being cast is so wide as to be "all except ____" where a whitelist is usually seen as "none except ____".
Think of it as shorthand for a list that expands to be infinitely large. [0]
People would consider a blacklist that includes ` * .example.com` to be a list that contains all potential subdomains of `example.com`. With ` * ` being seen as shorthand.
E: Spaces around the asterisk added to avoid HN formatting.
[0] Technical limitations aside, especially in the context of URL matching since URLs have a maximum character length.
If it's not a joke, it's at least an exercise in absurdity.
I wrote a regex that would allow things that aren't facebook, and then you said "No, you're not allowing things that aren't facebook, you're not allowing things that don't match not being facebook".
If it's not a white-list, it's at least an opposite-of-black-list.
If you think you need a blacklist you should probably be using a whitelist. If your problem can't be solved with a whitelist then it's probably better solved in a way that doesn't involve a blacklist or a whitelist.
How do you turn around a hardware company, you dont. But it wont die either ... software rises and falls like a deritive stock, but hardwate is like the gold tgat is always good to have a stake in
My suggestion would be to become the mysql of hardware, be compatible with everyone, what if an hp could go from pc to mac? We have never had that direction. Impossible you say? That why theres profit , the market doesnt have it yet. (Mac to pc is there)
Cheaper hardware , but same env. Make it worth apples wild. Hp seems to have good salesmen and bizz connects. Big contracts are not just about tech.
I offer a middle path , a bhudist interpertation of the problem. A project can be both fun/innovative and productive. You iterate on the fun , then you iterate on the productive. Youll never acheive completeness in both. Youll always suffer from needing to improve on aspect. Life is suffering , learn to accept and not let that reality stop you from creating.
But some projects are more innovative or productive than others. Maybe you should abstract those projects away from eachother? You could put them in seperate classes. You could have the productive project use the innovative project.
The cog load should be fairly similar weather you jave micro or monolith.
There are good and bad abstractions but in the end the cog load is a sum of the leaves and this never changes in the tree. In fact the cog load is better with bad abstraction , or no abstraction.
Hard coding is no cog load. Its in that file that function for that feature.