Some day, everything will belong to only a few people and the rest of us will be their slaves. But maybe at this time or some day before, some might recognize, that living on profits alone is not possible.
> Agile doesn't mean "every engineer working on whatever they wanted."
I totally agree. In my experience, it is very dependent on the group. When you are unlucky, you are in a group where for example one person always grabs the interesting parts. Because the group decides, it is very much about group pressure and clashing interests. A bad agile group can be similar harmful as a bad project manager.
One of the worst project managers, I experienced, insisted to divide the work "evenly" to the people in the group -- totally disregarding experience and abilities of the people. In a bad agile group, similar effects can happen.
In non-agile projects, there are dysfunctional groups and in agile projects there can be -- but in the later case, the problems can be worsened.
As I experienced Scrum in practice, it is said that people should be "empowered". In reality, something totally different is happening: People are not empowered, but the management just delegates the responsibilities for the project to the developers and lays back, assured that they just have to wait for the "agile fruits" to be reaped. They have done everything, they could do, now the "empowered" employees have to see ...
Those poor employees might feel "empowered", but in reality, they are "impoverished". They are now responsible for the project, but often without amble resources needed. For example, when they need additional hardware or rooms or .... they are not empowered to get it. They are still beggars. Instead, they are empowered to work longer hours to reach the project goals they have set themselves. Why did they such a stupid thing? Because they wanted to look bright or because of group pressure or because they want a raise ...
And after they set their goals themselves, they are on their own.
This is not "empowerment", it is not about people -- it is just a good excuse for the management to get rid of the responsibilities and to "motivate" people to work longer hours. It is the newest "silver bullet" process of a project management that already lost control.
This. 1000x. This is definitely one of the pitfalls of poorly implemented scrum. For bigger companies, scrum tends to be a decision by the higher ups and implemented by the lower ranks keeping middle management is disarray over their role in the change. Moreover as the author mentions agile is about people first, but followed by processes. If scrum teams don't have the power, or empowerment, to change the processes, to become more agile, to remove blockers/impediments, the team burns out / self destructs for the precise reason you mention about spending longer hours achieve the committed (not to mention the committed is affected by the deadlines which are manipulated by management/or worse, external stakeholders) in order to uphold their word/project. To me there is a flaw here.
This is really the heart of it, I've really only worked in environments that have been top down as their implementation of scrum. When the engineer team got to decide, we picked Kanban. The lightest process for us.
Scrum top down. I buy that. Bottom up? I'd give it a try, but the team needs the ability to say "no".
I think, the freemium model works best, when the resources needed for one additional customer (including computing-power, storage and support) are relatively negligible.
Many companies operate the freemium model with much less than 11% conversion rate -- but the additional customers they have to carry with the others are not so a heavy burden.
The advantage of the freemium model is faster scaling and adoption of the service -- but with the cost of an additional burden ... and you have to know, if your business can carry the weight or has to do differently.
One question on behalf of this: Has anybody experiences with mixing RAM types today? My problem is, that new computers most of the time come with 4GB pre-installed (1 module), but I want to have 8GB. Get the same RAM (DDR3) is rather unlikely -- so, would you add a different RAM module to the preexisting memory module or is it better to replace it with a pair of new RAM modules?
My experience comes from an Ivy Bridge machine with a B75 chipset and 4 RAM slots, YMMV.
I had a single 2GB 1333MHz stick and bought another one second-hand. The sticks had different densities (one had 4 and the other 8 memory chips on) but timings were the same. The system would not boot with the sticks on the same bank (same slot color) but when I moved one stick to a different bank, the system booted and BIOS indicated the memory was operating in dual channel mode at correct timings. I didn't experience any issues with the system for 1 year.
If your machine only has two RAM slots with a single bank, then it's a crapshoot on whether the system will boot. With two different banks you can usually mix non-matching memory.
Unfortunately, the computer I am about to buy has only one bank (smaller size computer). I also was thinking about using the dual channel mode -- but as the speedup would not be that great, I could do without. But I guess too, usage of different modules on the same bank might be a crapshot.
The guy who sells me ram suggested I don't buy two of the same 4gb modules but the 8GB(2x4) kit of the same brand for £1 more as they're tested together. Read into that what you will.
Just get the additional RAM from the same vendor (or Crucial or Kingston). Your mainboard will automatically change the settings to the lowest common detominator so it will work just fine.
Not to mention, when you manage to get a "BadUSB" -- in this case you might be doomed ... you might even don't recognize, that a strange force have taken control of your computer and internet connect.
But those agreements all have a common agenda -- don't think about geography, but about the common agenda behind it. We are living in the era of globalization and one of the reasons for such treaties is, that the geographical differences should vanish.
Of course it is not about the same agreement -- but this video sheds a light about all those agreements.
Ok, lets just never have another trade agreement in the history of the world. That should do it. Clearly all of them are bad. We can prove it because some of them are bad.
Yea, and I see this as one of the main reasons, the quality of work is declining instead of improving (due to technical advances). In my country, when you build a building today, you hire a builder company. This company does no building themselves. They buy the parts of the building from subcontractors and some times the subcontractors buy the service needed from sub-subcontractors. And the company that finally does the job, some times, they even do it not with their own workers, but hire some cheap temporary staff to do the work.
So finally, who is to blame, when the window is not even? The builder? No! He did nothing. The windowing subcontractor?? Technical yes, but practical he just used hired workers. Some times ago, it was possible to say: Here we have a good company, with good reputation, the workers are proud to work for it ... Today, it is just a blaming game -- and when one of the subcontractors is sued because of bad work, they file bankruptcy, because there is also no financial basis -- the companies are just empty shells.
What also adds up to this is, that on every level of this game, only the price of the service is evaluated today -- not the quality. I also saw cases, where the builder company was a big one with great reputation, but the execution was awful! The reason: Bad contractors.
Another reason in my country is, that the requirements for workers in the building sector have been deliberately drastically lowered by the government, to make way for even cheaper work.
Today, (at least in my country) one that wants a house for his family to be build, has no means to decide, if the company will succeed and make a good house or will build a horror house. In most cases, there will be several topics where the execution was bad or really bad and you can call yourself lucky, when the additional costs after the house was finalized are moderate.
There are some really bad cases, where families thought the house would be ready in time and canceled their rent-flat just to be on the streets afterwards, because their house was not ready even months after the deadline. Some where never finished.
Today, it seems, that many people just have one principle that holds above anything else: Money. I think, this way, we ultimately sell out humanity.