SonnyWortzik

Some people just don't get the difference between Privacy and Anonymity.

Frontpage wow, that was my go to back in the days. Then I saw the markup it was making, yikes!!

Everyone learns differently with a combination of what you mentioned. visual aids, auditory aids, reading. There is no secret to learning only that you are consistent.

There are times that a technical manual comes along and there is a need to go off into the bowels of other technical information that is also provided and that to me does not help in any way. I must learn what I set my eyes out to learn and nothing more. The rest comes naturally as I begin to experiment and running into the same learning curve as others. That is when I begin to dig a little deeper. Again with all of the aids available, visual audio, reading and experimenting, until I feel that I have a strong grasp on that specific subject.

There is no secret, the only thing I suggest is to stay on it, and stay consistent. The more you do it the more understanding you will get. There is truth behind "practice makes perfection".

I am hoping this is just an introductory set, and if the demand is there they would make a bigger one. I am with you. I want a detailed set. 3000+ pieces

sure, but Chrome has the power of Google behind it and that makes the browser more attractive because users feel that if the browser comes from the search engine company they already use then it must be compatible with everything they do online. This is a perception which gives Chrome an advantage over other browsers.

It's a bit of a monopoly that Google has on the browser market and so now they have leverage over what gets approved and implemented in those browsers.

Since most people use Chrome then other browsers are forced to follow suit with compatibility.

In this highly competitive industry, you cannot expect someone to just stand up and demand to not be exploited when they can be simply fired and replaced within minutes. So no, it is not as simple as just growing a spine.

Based on the recent article by Jason Schreier (Kotaku) about the complete disaster of Anthem game development, it puts into light the mismanagement and the exploitation of these developers to churn out games as if it were a factory floor with little time and pressured to deliver.

These developers are talented but you can only do so much with that talent when you have no time to demonstrate that talent and are being asked very unreasonable demands to deliver. Only to deliver a half baked product and asking their customers to dish-out $60+ to be a "beta" tester for a company racking up billions.

This unionization is a must. This exploitation has to stop.

> collective action problems where coordination benefits every company in a way that individual action wouldn't

Remember we are talking about Capitalist corporations that answer to investors.

Your point is great if there is an incentive to only benefit the consumer. The benefit in this case is to maximize profit at all cost. Profit creed(not greed) is to ingrained the need to maximize profit. Because of that, greed is the ultimate driver against achieving 'self regulation', hence the reason why we have gov regulations in the first place.

Necessity is the mother of all inventions. I am glad to see some are skipping politics and actually trying to solve this with some intelligence.

c'mon lets get real, 'Self Regulating' means someone actually has to be honest of something but as long as there is profit to be made, honesty takes a back seat.

There is a yt video that I found very well done and explained very well. He goes very deep in the inner workings of javascript.

I think you will like it. It is "modern" but not a new video. It is probably about 3 years old. Still relevant. He has a udemy course for $10 bucks.

https://www.youtube.com/watch?v=Bv_5Zv5c-Ts

ahh nice, didn't know that. learned something new today.

This is in good fun. What is wrong? I mean the original post is not really a Scientific Journal article. It was posted for fun. So lets have fun once in a while.

Here is how I pictured it going.

> operator: "911 what is your emergency?"

> "...........Hello, I need assistance??"

> operator "Sir, Sir. Do you need help?"

> "........... YES I am here, Who is this? ......."

> operator: "Sir, we began tracing your call and are on the way.... wait... Sir what is your current location"

> "uuuummmmmm.... well about 2000 km up..... Sorry dialed the wrong number..." hung up

> operator: ".....???"

isn't day dreaming fun? LOL

My vision of the future for the cleaning service industry:

Robot at home on stand by a la I,Robot movie

:"Good morning Mr. Anderson, our remote cleaning specialist is ready to clean your home, do you comply?"

pass code confirmation needed

:"Thank you, our services will take approximately 45 minutes. Please stand clear while we complete our task. Thank you Mr. Anderson. Have a Wonderful day!"

:"Please note that your next remote cleaning will require a renewal of your service agreement. Please take time to fill in the survey, confirm your subscription, and adjust your cleaning times, and thank you again for being a valued customer here at CleanTech"

LOL day dreaming is fun.

Integration. It is all about the integration. M$ platform is so tightly coupled that many companies see the value in spending on this tight integration than spending it on 25 different Engineers to manage their 40 vendors that may be needed to run some of these applications and platforms.

Dealing with one vendor, M$, is better than dealing with 20. You pay for one support package and get all the benefits that come with one platform.

As much as I love open source, I do see the benefit of working with one vendor on all of your stack needs.

M$ reporting systems of SSRS SSIS and other is probably their bread and butter when it comes to DB space. Very few want to spend 60-70 hours a week building complex command line reports where with SSRS and SSIS most of these tools come with a nice GUI that helps you build these reports. Sure there are others that do the same but most required a third party vendor to add to the functionality. For example Apache. With Java and Apache I've had to deal with literally 15 to 20 different vendors just to do the same thing I can do with one vendor. Jenkins, Zookeeper, Camel, Cassandra, Tomcat all under the banner of Apache, but in reality governed by their own set of standards. I mean take a look for your self: https://www.apache.org/index.html#projects-list

biodegradable cups? Is that possible?

I never got around to using Mongo as my main doc db because it was incredibly hard to find a management tool.

I now use json supported functions in SQL Server and do not have the need for a different type of database. SQL Server handles my small 'documents db' implementation with the infrastructure of a RDMS. Win win for me.

To me Mongo just got popular by mistake way too early. It's like having a celebrity retweet your post because they liked what they saw at the time, exposing you to the world where everyone now thinks you have something important to say. Not surprisingly, you don't!

I used El.OS for 3 straight years and had to drop it for business reasons. The OS is excellent. Highly recommend it if you are not bound by your business needs.

They do, and we do. But the mass sheep audience does not. All they know is: "Does the link work?" and "Can I share it?" That's all.

"By very definition, it is about paying a person in a position of power to make a decision that is in your favor."

Why do you think that is? Is it Ideology? Or is it just profitable to get that decision in their favor?

What is common about their corruption and ours that you notice?

Most think that corruption is the problem when in fact corruption is just a symptom.

In social change this is the only one that matters:

"(what is profitable)" all other "forces" are bound by this at systemic level.

> "(what is considered ethical)"

it can only function if you go back to "what is profitable" because if it is not ethical and there is no law to prevent it then it will be done because it is profitable.

If it is ethical, and it is not profitable, you can rest assure it will not be pursued not matter how good you feel.

Example: Feed the hungry, it is a great ethical idea, but it is seldom profitable so you do not see any company going out of their way to invest in feeding the hungry.

> "(what is legal)"

this also runs only on what is profitable. If it is not legal, but it is profitable then you can be sure that the laws will soon be changed to accommodate. i.e. Cannabis movement.

> "(what is technically possible)"

also runs on what is profitable. We can technically do anything we want but is it profitable?

Don't be fooled by these articles that find a "novel" way of looking at the problem. It is just noise. If you can't fix the monetary policy in the world, then "what is profitable" will always be what drives any social change

You make quite a lot of assumptions with 2 and 4. I was one of those inexperienced. Not as a developer but of the architecture of micro-services. As a technical lead I did not have the visibility of the cost and organizational effort into a micro-service architecture. I just started developing an architecture for our current project domain because we needed the flexibility of deploying these components separately.

But upon pitching the idea to an Organization Solution Architect VP he quickly stopped me and demonstrated me the cost of this effort and he did not have to demonstrate the effort because I went through similar challenges with in my team, and so expanding that effort into the entire organization would have been a massive undertaking.

So he did not shoot down the idea he just wants to take it down a notch and start with compartments, and not the entire organization.

quite common. Many of my colleagues including myself will sign up for a course online only because we saw an interesting topic in one of their modules. We go straight for the module, learn what we want and move on, never complete the course.

Start with the support backlog.

There is no better source of knowledge than solving software issues. You see it all in that backlog. Deployment issue, build issues, bug fixes, feature changes, merging problems, log files, web server configurations, DNS issues, certificate installations, database errors, database updates, connection issues, you name it. It is in there.

Once you feel comfortable with that backlog, look at the source code of your application and you will then ask your self, WHY IN THE WORLD WAS THIs BUILT THIS WAY?!?! you will find everything wrong with the application and that is a good feeling.

Start with Supporting an application before developing it.

oh just turn it on an use it huh? And collect all of my web queries. Clever. Yet another mass collection scheme by Alphabet. I have to give it to Google(the real company here), they sure know how to embed themselves everywhere in your life.

I have three rules for better coding performance, for me.

- Ask Questions

- Do not Multitask. One problem at a time.

- Test control answers i.e. You want result to be 10 then test for 9 and 11. Wrong results create a more stable solution.

Speed has never been my strong suit, but when I deliver code to QA, you can bet that you will be testing a well thought out solution.

While your data is being stolen and sold in the dark web, Equifax is happy to sell you Identity protection for your business: https://www.equifax.com/business/credit-monitoring-and-ident...

We joke a lot about that after I was hired as a middle aged coder...

during interview

Boss: "so do you think you can fit in this culture?"

Me: "You mean, do I wear skinny jeans and drink kale smoothies? Probably not, but if you want your work done, does culture fit matter when you have a mile long back log?"

Boss: "good point, so... How does your schedule look for next week?"

it was all history from there.