mizchief2

Article does nothing to debunk any of the "myths" just offers suggestions as to why you might not trust any scientific study.

that's it i'm canceling my account with them. Their scores are way off, they just use you as a way to sell more credit cards, and now they are giving out my info. They are worse than useless now.

You would think but apparently that doesn't apply anymore. You can control the content and still get the protections of a common carrier.

I just know I'll remember that cloudflare could pull the pulg on my site if one of my users posts something they don't like. I don't think I can recommend their service to any of clients because of that.

Its too late for that. There is already a lot of federal control and influence over local police stations. You really think every po-dunk town can afford those MRAP's and other military equipment?

That is the same argument made to debunk climate change science. As if people dependent on a theory being true would set aside their morals and say that theory is true.

I don't think so. The US has used drones to bomb a lot of people without having to risk their own personnel and reduces the backlash from its own public.

estimating is either easy or impossible. You either have done it repeatedly and have data to show how long it took, or you have no fucking clue.

Focusing on the most important features of each module first, and then the most important of the next then the next with a focus on progress towards something useful is the only way to go.

When you have a consistent team and some tracking data to compare task size to hours required to complete, then you can start doing estimates for future work, but you never have to ask the dev team to estimate other than setting some relative size between tasks and trying to stick to the sizing system. I prefer Fibonacci story points, but it can be anything that has a number.

The whole point of Agile is to force the entire organization to recognize the fact that we don't know how long it will take to crate a satisfactory product. That doesn't mean just dev time but also figuring out what you want it to actually do throughout the process.

Instead of thinking you can write a perfect requirements document, then can just design and build it (waterfall) doesn't work.

The idea that you can have any sort of meaningful estimate even when you don't have perfect requirements is insane. Having an estimate with perfect requirements doesn't even work.

The most effectivly analogy I've used lately is: "Take your car to a mechanic and say "My car is making a funny noise, how long will it take to fix?" and see what kind of response you get"

I wasn't really on board with banning Huawei until I read this article.

I think Mitch Hedberg described it best:

https://www.azquotes.com/picture-quotes/quote-when-you-re-in...

Then the other side is giving you a "small project" that takes the better part of a day to implement. I just pass on those as well, and i'll do the short challenges but I don't really take the company seriously after that.

I found the most effective is whiteboard sessions that actually somewhat resemble reality as if I was the Product Owner and/or Architect with a problem. Then go through the design process, what database system would you use, would it have a a web service or be microservices or whatever, dig into the database design etc. May ask more specific technical questions along the way that are relevant to the design.

but the main thing is there is almost no actual coding done in the interview process at all.

As a country it is just good resource strategy to use up all the resources that are cheap to get in other countries first so when they start to run out, not only do you have a source that is close to home and easy to get, but you can now sell your resources at the higher price.

If we build enough Nuclear power plants climate change wouldn't be an issue

Sounds a lot like the "self evaluation" nonsense when it comes to performance review.

"I give myself a 5 and deserve a 5% raise" Oh well you only get a 2% raise.

Just lazy management that event "delegates" the only part of the job they are actually supposed to do.

Maybe the numbers don't work out but using excess energy created by wind solar etc. to offset the carbon produced by coal burning when we need power but the wind isn't blowing or the sun isn't shining could be a promising idea.

Could be a cheaper alternative to massive battery storage if the desired effect is to always have energy in a way that produces the lowest amount of CO2

Further shows that many environmentalists care more about controlling the economy than helping the environment. Being able to utilize fossil fuels without the carbon issues should be great news, but instead people are worried that it won't kill off our means of producing power fast enough.

Why is the story that Boeing sold them as extras instead of the airlines not buying the option?

I don't understand the obsession with laying high-speed rail all across the US when we have perfectly good airplanes and a massive network of airports.

Not sure what I'm missing here. "superposition" is more of an explanation of not knowing the result of a measurement until it is measured. So saying that one person performing the measurement and not telling someone else what is was, so that person sees it as in the "superposition" state vs. the measured state is not two conflicting realities. One person just has access to different facts.

If I witnessed a murder and withheld that information, and someone else thinks the person committed suicide based on the evidence they have, we aren't living in two different realities.

This is why you need to get the government out of business. They shouldn't be choosing what stores are built where nor should they be giving certain businesses tax breaks over others.

With my 4 year software engineering degree I learned c++ and java which I never used professionally. But I also learned about data structures, assembly, OS design, QA, OOP, design patterns, software project management, etc. as well as physics, chemistry, calculus, psychology, literature, etc.

Learning the syntax of the current hot language over 4 months is not an equivalent to deep understanding of CS or just good problem solving in general learned over 4 years.

I don't really support artificial cash injections into the system, but I do agree that if you are going to do that, doing so from the bottom vs. the top will create a greater lasting effect, or at least benefit more people in the short term after a major and sudden recession.

Imagine where we would be if instead of baling out the banks after 2008, letting those banks fail and forgiving the loans they held. Millions of Americans owning their houses free and clear as well a having an extra few thousand dollars a month to spend or save.

I think that the problem is that the middle class is experiencing the "real" growth rate of the economy, and the top classes are just getting the benefits of all of the QE and other tricks on the monetary system.

First of all, if you enjoy this project keep at it. What you learn in the process will be more valuable to you than any advise you get from the naysayers.

However, don't expect everyone to jump on it. The original purpose of Node was to provide a simple way of handling I/O in a non-blocking fashioned without having to deal with the headache of true multi-threaded programming. So you are trying to re-write the engine to do the exact opposite of what it was created for.

Won't marry a woman who would want to waste money on a shiny rock.

Encryption.

Supply and Demand. The same reason for everything else that goes up in price. Government subsidies created more students who have the means to go to college where previously they would have gone to a trade school or learned a craft on the job. While at the same time public schools have gotten more lax on grading so that students can get these grants and scholarships.

As a manager I've had a recruiter basically say "That's a nice development department you have there, shame if something were to happen to it." As he described that by signing a contract with him and keeping "active" by hiring his candidates a couple of times a year, he would not solicit the developers at my company.

With your experience you will likely know the right course of action to take immediately, but will still have to reach consensus with the team to keep them engaged as solving the problem is the fun part.

Get good a steering the conversation to your solution vs. just handing it down. You know the whole making it seem like it was their idea thing.

If your team perceives you as an authoritarian, they will be afraid to make any decisions on their own and you will become a constant roadblock.

Nobody drives; there is too much traffic