352 karma · joined August 16, 2012
Edit: sometimes it's a good idea to call ahead and ask for "uninsured quote", you would be surprised your $200/visit physician might only charge $50 to someone without insurance.
Could you please point us to the source of this information?
It was my understanding, from a news article I read a few years ago, that Medicare evaluates each medical procedure and comes out with a fair price that guarantees fair profit for the provider.
I think it might be that providers cannot charge insane profits to Medicare so they rather avoid dealing with them.
I landed a gig related to Azure training and it's keeping me almost full-time busy right now. Considering this is the holidays there is a good chance we will be even busier next year.
Well, this was the sentiment of most Americans after World War 1. It took the attack on Perl Harbor for Roosevelt to have enough support from congress to join WWII.
I think that after WWII the US government made part of its foreign policy to use economic integration and military might to prevent any country from ever dragging them into WWIII.
I am personally not worried about China, Russia, the middle east or even North Korea. But I would be seriously worried to see Japan rebuild their military because we pulled our bases out of there.
I think Valve has done an outstanding job, unfortunately, other game studios and controller manufacturers don't seem to care.
For example Logitech gaming wheels don't support linux. Although there are pretty good reverse engineered drivers, last time I tried, force feedback support was hard to get configured and didn't work as well in games such as Euro Truck and American Truck, which have linux versions.
Now, like the OP, I had encounters with windows 10 forced updates: I stream on twitch and I recall at least one time where, from my viewers point of view, my stream abruptly terminated. Turns out Windows 10 decided to update itself locking my computer for at least 1 hr.
There are programming languages, frameworks and tools which would be unlikely to exist without "advances" such as TDD.
I agree, while a very simple process, people who don't get it tend to complicate it. They focus on the process instead of the result.
Most failed scrum teams I've seen out there skip the retrospective meeting, which is in my opinion, the key of the whole thing: that's the meeting where team members usually realize they "own" the process and can steer it any way they desire.
The exercise of just enumerating in a couple minutes all the steps to complete such a story gives everybody, including the one who is going to do the job a clear idea of the effort or whether they need more information before proceeding.
Btw, while Scrum is great for software development, they are not ideal for maintenance and/or infrastructure management where a defined process such as waterfall might work better. Trouble tickets and bug fixes should be kept outside the sprint unless they become stories.
Here is a quick 4 step planning meeting process based on planning poker:
1. Pick story from backlog, explain in a couple minutes what do you think would take to implement it.
2. Team members pick an estimate of the effort.
3. If there is consensus, note estimate on story, pick next, goto 1.
4. If there is no consensus on estimate, have highest and lowest explain why they picked their estimate, goto 2.
If you are expending more than 5 minutes on a story and there is no estimate, push it down and move on. It's not ready for development. The whole planning meeting should not take more than 1 hr.
This process, allows everybody involved in development to have an idea of the overall project and chip in with their experience to impact estimates (this might require refactoring class X, it might be hard to test, will conflict with Y and Z, etc)
Story points are a measure of "relative amounts of effort". A 2 point story is twice as hard, as far as effort to implement it than a 1 point one.
> Scrum meetings (aka rituals) have been among the most miserable hours of my life...
Would you rather have many meetings almost every day, or a single big ol' meeting every few weeks so you can focus on coding without interruptions?
> The review meeting causes utterly unnecessary anxiety (Oh my god, will my feature work?)
It should not cause anxiety because it MUST work. The review meeting is to show stakeholders a "potentially shippable product increment". Everything you show on the review meeting should have been extensively tested already.
> Why estimate stories that you are going to break down anyway?
You only break down stories if they are too big. You are not supposed to work every detail on a planning meeting.
> but in Scrum, the retro is explicitly supposed to be about the Scrum process itself, not about the codebase
The retro is not about the scrum process but about how it is working for the team. All these issues you have already complained about should be reserved for this meeting where the whole team can decide which adjustments to make.
> The main goal of Scrum is to minimize risk and make sure the developers do not deviate from the plan. I will come back to "Scrum controlmania" later.
It is regretful that, like all the other "why scrum sucks" posts I've seen on HN, it all boils down to a bad scrummaster not managing expectations and taking the time to explain where the process really comes from.
Scrum was "designed" by Ken Schwaber, a software project manager at the time looking for a better way to control software development processes.
Schwaber discovered he could use an empirical process, rather than a defined one, to control software projects. He created Scrum following this principles.
While this would ban current fuel burning technology, it might allow for someone to come up with a car engine or coal turbine that doesn't release anything.
I think banning any technology is a bad idea. Imho, the problem with climate change is not the burning of oil or carbon, but the emissions from doing it.
Then I noticed the test was expressing constraints using time/space complexity, concepts I was completely unaware about for my previous 15+ years in the profession.
So now I am reading about algorithm theory face-palming at the realization I have reinvented the wheel many times during my career instead of just re-using a PhD. researched algorithm.
They tried this during the dot-com boom of the late 90's... I don't think it worked out too well.
They hired just about anyone and paid crazy rates. You could point them out for showing up their first day carrying a "learn ASP in 24 hrs" book.
Fortunately, the dot-com bust weeded them out. Most of these people went back to sell cars or whatever they were doing before while we had to clean out their messes.
But I still tend to fall back into it when I'm reading something hard to understand, specially when reading english which is not my native language.
The book[1] claimed you could reach up to 1200 wpm by doing all the exercises, I never got to finish all of them.
[1] "Superlectura veloz" (fast super-reading) - Carlos Quiroga
I took on speed reading in college after realizing I needed to study and learn faster or I would fail miserably. The book I picked up seemed like a lot of common sense steps the first one being to inhibiting subvocalization, the internal voice we are used to hear while reading since we where taught to read out loud. The idea here being that our mind can process information much faster than the speed of speech.
The paper cites several studies that suggest inhibiting subvocalization reduces comprehension. However it takes the result of these studies as fact when they might be flawed. An example in their chapter about the role of phonology:
> First, consider a study in which skilled readers were asked to indicate (with a button press) whether briefly presented words were members of a certain category (e.g., foods; Van Orden, 1987). The people in this study incorrectly responded “yes” to a word that was not a member of the category (e.g., meet for the category food) about 19% of the time if that word was a homophone of a true member of the category: In this example, meet is pronounced the same as meat, which is a food. Incorrect “yes” responses to non-homophone words—for example, melt—occurred only 3% of the time.
I looked a the Van Order paper (http://link.springer.com/article/10.3758/BF03197716) since it shows the highest reading comprehension failure rate (19%). They came up with that number from an experiment studing just 5 male and 5 female undergraduate students (see Experiment 1, page 3)
I think citing this study altogether as a basis of one of their main conclusions (eliminating subvocalization lowers comprehension) is flawed: The study didn't compare regular undergraduates with speed readers (people skilled at comprehending without subvocalizing), it just concluded no subvocalization could lower comprehension by 19%.
Precisely. I find amusing how every time there is a trend up in the price, there is a flood of doom sayers, as though they want to force the price down...
I think the bitcoin network is fine. These issues will eventually be resolved, although not likely to OP's satisfaction or the way he wants to solve them.
"Individuals and interactions over processes and tools"
I think that is a little extreme but I agree the system is way out of hand, specially in duration of copyright terms.
Copyright was supposed to allow artists to earn a living off their craft instead of relaying on being sponsored by the local nobility. It is not supposed to make you rich.
Client and servers using this protocol would not be required to implement SMTP/POP/IMAP at all, bridge services could be built for that.
> It aims to be compatible with the IMAP data model,
Unlike this project, I think user requirements should drive the protocol's design, not a need to be compatible with SMTP/IMAP.