> More like Italians from New York were never part of USA (they were).
Please re-read my statement that you quoted. Italians from New York is completely different from Albanians from Albania. Albania is a country where the overwhelming majority is Albanian.
> Never integrated, always closer to Albania.
Whether the Albanian population in ex-Yu showed inclination towards Albania can be argued either way, but I don't see the Albanian population in Macedonia do the same thing (took up arms and fought at the risk of losing their lives for independence).
Considering someone alien makes it much easier to segregate, ostracize, denigrate, punish and abuse them. Ask yourself whether the ex-Yu government would have been able to do the things they did to Kosovo if they have called them our brothers (or even called them citizens of Yugoslavia) or if they called them "those Kosovo aliens that don't want to integrate".
-a Albanians from Albania have nothing to do with Yugoslavia, it's like saying Italians from italy weren't ever really a part of France.
-b From the comments it looks like Albanians from Kosovo weren't the only ones who didn't like the government of Yugoslavia from that period. If the government doesn't foster inclusion and cooperation, then fractures happen, whether you're "part" of the prevailing culture or not. Albanians were not a minority in Kosovo, the same way that Slovenes are not a minority in Slovenia (and I think you'll agree that the size of the population is similar).
The way I see it, if the pension fund has less money there's less to manage and also less to gain from. If the people flee to private investments, they do not necessarily flee to Blackrock.
I read it and I couldn't shake the feeling of an opinionated piece.
It's very likely that the definition of what encompasses Root Cause Analysis (RCA) differs between the author and me. It's likely that he sees the RCA as a top-down managerial tool that is used to find fault or point fingers, as opposed to a good-will exercise between team members (spanning one or few teams) that is used to find areas that are more "fragile" to the current processes and evaluate if it's possible to strengthen them and make them more resilient. In this context, RCA becomes very similar to the other concept used in the article which is "Post-incident review".
RCA imo also helps define better the responsibilities and areas of expertise of different members and what would be acceptable actions and escalations in similar scenarios.
>In fact the person who wrote the offending line of configuration had recently adopted a new cat, who had been keeping them up late the night before, so perhaps the real ‘root cause’ is the cat?
The RCA would help identify the person as a potential single-point of failure and evaluate if additional things can be introduced to make it more resilient and reduce the probability of the issue happening (have a pair make the change, or have better testing before implementing it, etc).
That said, RCA should also take into account the rarity of the issue, and sometimes the conclusion is that no change to the process, etc is required since it would introduce more complexity and potential weaknesses in other areas, than it would provide additional benefits.
In addition, I find the following statement a bit too strong
> let’s differentiate between the ‘root cause’ and Least Effort to Remediate (LER). As long as an incident is ongoing, LER is absolutely the right thing to pursue. When the building is on fire, put the fire out as quickly as possible.
This assumes that all incidents are of "building on fire" type, and that's not true in my book. If the author assumes that RCA is used only for critical issues, that's not the same definition I've used. The course of action to solve various incidents is a "it depends..", such as on the gravity of the issue and what is the available timeframe to fix it, whether LER is something that you have already identified or that you need to find, the level of effort for LER vs identifying root cause and the potential for the applied remediation to cause other issues... heck you might even decide that it's better if you just let the building burn then try to put out the fire...
Despite the fact that there were various areas where I didn't agree with the conclusions that the author reached, I'm thankful for the effort that the author has put in this piece and for making public his point of view on this topic.
Not sure how I feel about this article... there are some valid points, but also some half-truths, where the answer is more "it depends" than yes or no.
The feeling I get is that the article tries to make a long list of all possible causes, which dilutes the main reasons why premature optimisation or even optimisation is skipped. It also doesn't try to see the issue from the other side and inform the reader when optimisation is premature and doesn't need to be considered, which makes its argument very one-sided.
One additional point that I think might be missing from this list imo, is the shifting functionality requirements given to the developers which make it less certain that a specific piece of code will be the foundation on which you will build the rest of the logic or whether it will be a leaf-level logic that will be used very infrequently but this comes with other caveats regarding refactoring, etc.
Personal opinion or anecdata:
Is it possible that communication is "detested" because it's not valued within the developer group? Many times, when someone speaks of a 10x software engineer, the gut feeling is of someone that provides the output (measurable in code) of 10 developers, not that he's able to have an impact in the organization through communication as 10 developers (breaking silo-s, syncing teams, etc), although this might be closer to the truth and what the duties of some staff and principal level developers includes.
In addition, rarely communication is valued within the companies where we work. Most aspects of documentation, whether vocal or written, are hard to measure and as such are ignored when an evaluation of the "worth" of an IC is done.
Personally, I think communication is relevant, but I also think that it's hard for developers to resist the sculpting that companies deliver to the employees on what is relevant in this field.
Agree with a comment that said to throw money at the problem, babysitter or whatever. It helps _if_ money is not a big problem. I used to be a lot more careful with money but since kids, I timebox the amount of time I spend on any thing that I need to spend money even if the end result means I'm leaving some more money on the table. Peace of mind is the ultimate goal.
Identify things that are really important to you (almost at a ruthless level), and shortcut/ignore the rest. This means prioritizing also time to relax (walk, read a book, meditate or whatever you do to relax) even if there are other things/chores that are in queue. Accept that some things will be delayed or not be done in the next few months until you get back to your footing. Recognize that during burnout, your efficiency is 50%, so reduce your load accordingly.
A comment I read a while ago in HN is "don't be the person that cares the most about things". While I don't think it applies to all issues, I apply it to some things. Try to apply the 80/20 (20% effort for 80% of work done)
Personally, during burnout, I've gone almost in survival mode. I completely cut alcohol (even beer), soft drinks, etc, try to sleep well, and try to exercise (or walk) just because it improves my energy levels.
If small kids that require lots of attention, consider babysitter, kindergarden or take them to the park (if there's one close by) during the time you are in charge. Personally I find that kids require less effort/energy outdoors. Youtube videos are also useful in a pinch (see "super simple songs" or "cocomelon" which have 1hr long videos)... try not to let them see more than 1-2hrs per day.
Regarding wife, when you're burned out, things look more pessimistic and you're less likely to let something slide. Maybe she's also overwhelmed and/or burned out and/or in "ruthless/survivor" mode. See if there are things that she's doing that can be delegated through money (order food instead of cooking, get someone to help clean/laundry, etc). If she gets some time back, she might be more able/willing to help with the load. Recognize that priorities are not the same, I personally don't care much about cleaning but my wife does. Try to always communicate...
Remember that if your burnout gets worse, it will be worse not only for you but also for your family ...
All said, I'm just someone on the internet that doesn't know much about your situation, so take everything with a grain of salt.
Personally, when I've been burned out, the cause hasn't been a single factor and it was gradual. Not sure if this was mentioned in the prior comments, but imo the first person that you should discuss this with is your wife and depending on how close you are, the rest of your support system (friends, other family). E.g. wife might agree to take over some larger load, look after the kids instead of you for larger period of time, provide you more space or not nag you for some projects that you were supposed to do.
The point is for them to provide support and to allow you to gradually get out of the burn out.
From my point of view, burn out is not a binary state and by alleviating some factors you can have a bigger recharge than what you spend. If you do any changes, try to be aware if you seeing any improvements and if not consider more drastic changes.
I wouldn't talk about this with my boss, unless the rest of the changes is not working.
I'm not an expert in the area and hadn't heard about Sailfish before, so I took a look and stumbled on this article [0] of Rosteltelekom (Russian national company) acquiring majority in the company Jolla that produces Sailfish OS, which makes everything about Sailfish a bit less enticing from a security perspective.
Another article [1] from a few months back says that Rosteltelekom owns about 45% and Jolla is trying to find another EU company to buy those shares, but didn't see anything more recent.
You might want to check Videostream for Chromecast ? There's both a mobile app that links to your PC and also a desktop app. Last time I checked, VLC also allowed casting of videos on your PC(although iirc was more iffy with subtitles, etc) though not sure if there's mobile support, and I believe there are also other paid apps that can be used to cast videos.
If you're referring to seeing videos directly from a hard drive without a PC, a TV with usb support should take care of that (long time ago, I had even a Bluray player that had usb and was used in similar fashion to cast videos from a usb flash drive)
Please re-read my statement that you quoted. Italians from New York is completely different from Albanians from Albania. Albania is a country where the overwhelming majority is Albanian.
> Never integrated, always closer to Albania.
Whether the Albanian population in ex-Yu showed inclination towards Albania can be argued either way, but I don't see the Albanian population in Macedonia do the same thing (took up arms and fought at the risk of losing their lives for independence). Considering someone alien makes it much easier to segregate, ostracize, denigrate, punish and abuse them. Ask yourself whether the ex-Yu government would have been able to do the things they did to Kosovo if they have called them our brothers (or even called them citizens of Yugoslavia) or if they called them "those Kosovo aliens that don't want to integrate".