6,940 karma · joined December 27, 2012
"Some people tell me it's inconsistent with human nature to operate this way--that people need to be protected from harsh truths and that such a system could never work in practice. Our experience--and our success--have proven them wrong."
That is from Principles by Ray Dalio about sensitive people being confronted with radical honesty.
Perseverance is not rewarded in software, at least not in JavaScript. The key reason is that there is no trust. Employers do not trust the competency of the developers and the developers do not trust each other. The result is that the work is typically extremely beginner and developers are not expected to write original code aside from trivial React components. Everything else, I mean this literally, is a downloaded NPM package because there is substantially greater trust in anonymous strangers than your coworkers. If you are interested/capable of doing more you aren't compatible with current hiring trends and will not be hired.
In all fairness though if you can get hired in a low cost of living market for 170k knowing almost nothing about how the software or the platform really work doing beginner chores then why bother persevering with hard work to be anything more? Eventually most of these people will elevate to management where their technical experience is irrelevant anyways.
To people who know what they are doing more code than necessary to accomplish a task is the code smell.
To people who are super insecure vanity code is required because patterns are memorized, so any deviation from the unnecessary boilerplate is the code smell.
"war" => "writing JavaScript"
"cold war" => "age of software"
locations => JavaScript framework namesSo what do you do, as a software manager, if you don’t trust your team? Do you set higher technical standards? Do you invest in training? Do you hold responsible for failure to deliver a certain level of quality?
DOM Scripting: Web Design with JavaScript and the Document Object Model by Jeremy Keith
Great book and interacting with the DOM is essential to performance in any kind of browser work. Unfortunately most developers today are completely terrified of the DOM, as in PTSD and need counseling terrified.
As the creator of a once extremely popular productivity tool I can firmly attest that being the creator of such tool is not a sufficient qualifier to elevate one to “expert” of the given problem space provided just 3 years time.
BTW, nobody is an expert within just 3 years. That is a key indicator of a Dunning-Kruger moment that becomes clear by drilling down just a bit into key performance indicators from research and experience.
Learning new capabilities implies things like transmission, storage, performance, distribution. New languages may unlock new capabilities your current language does not. To a far lesser extent this may include learning some new tool.
Frameworks are something you learn on the job to gel with a team or something you learn to be hired. Typically frameworks are an abstraction so that groups of people can execute against a common API, but otherwise are things you could do without faster and leaner as an individual.
The definition of mission critical is also misplaced. When I think of mission critical I think of Ada and Rust for something like running a nuclear power plant or dashboard of a fighter aircraft. In those cases failure is expensive and deadly, so code that works is an insufficient quality. The definition here though is shipping code that must work. Why would anybody ship code that doesn’t work?
https://github.com/prettydiff/wisdom/blob/master/Leadership_...
It seems that you completely misunderstood the study, a longitudinal study conducted over 5 years and compared against a real world factor outside the study: military awards irrespective of any study.
It’s not vastly different from other professions except software. Source: I have been in the U.S. Army for 25 years and I have been a corporate software developer for 16 years.
The only valid question is not what makes the military unique but instead what makes software unique. The answer: a complete absence of professionalism. I wrote about this here:
https://github.com/prettydiff/wisdom/blob/master/Leadership_...
Edit: corrected the hyperlink.
When that’s the target for hiring and the majority of people in professional practice any attempts to aggressively improve are frequently met with friction and do more to put your job at risk than just coasting. That’s why so many developers have side projects where they can be as ambitious as they wish completely disconnected from the boring professional work designed for 25%-ile.
Because it probably doesn’t apply to you. It’s not that programmers are in high demand but that hiring programmers is in high demand, which is massively different. It’s the difference between people who solve problems as compared to people who reproduce the same problems to solve.
* Intelligence gathering
* Foreign military disruption
* Infrastructure disruption
* Civilian misinformation campaigns
* Civilian commerce disruption
* Trade disruption
The goals of cyber warfare campaigns are typically limited by the proxy relationships between national powers. For example China has sophisticated cyber capabilities but do not want to do anything that will damage economic relationships which includes any form of political interference thereby largely limiting their threat to the US to military and intelligence operations.
When you consider there are many players each of whose goals are a combination of national priorities and political relationships this gets complicated.
* Go into academia and publish often. This will not pay well but you can do ok and you can enter the corporate world at a later time for a high salary but it will feel like working with children.
* Become a military officer. This is a highly focused lifestyle befitting an operationally minded person who lives in the moment with constant stress balanced against a cool resolve. If you want to enter senior management you will become a short term academic at CGSC and the war college in addition to your prior fast paced life. To summarize the military life is to condense real world career struggles into a quarter of the time, plus life and death consequences, but without the fear of becoming spontaneously unemployed. You won’t get wealthy in the military either, but you can become extremely well compensated (wealthy compared to average persons but dirt poor compared to the equivalent responsibilities in the corporate world).
* Become a JavaScript developer. As a JavaScript developer the incompetence is an industry norm so you can easily achieve a highly salary with minimal time investment. Salaries are inflated and expectations are low. JavaScript developers will often complain about stresses that do not seem to exist, as compared to the academic or military life, plainly indicating that stress is relative. This is the easy life unless the industry matures, at which point many developers will quickly find themselves disqualified from practice without a fallback option.
Examples:
* Page load achieved in 0.5 seconds
* All variables are explicitly typed, if in a loosely typed language.
* Does not use conventions X, Y, Z
* Defect resolutions will not be accepted without corresponding test automation coverage
* All type interfaces will be explicitly documented in markdown language immediately prior to the interface definition.
Another way to think about this is if you cannot automate your quality definitions they aren't that important, because you will almost certainly not enforce them.
Most developers seem to view quality as them not writing any code at all, which implies downloading everything off NPM (or some other package manager). My opinion on that differs, which is why its important to define what you mean by quality.
It’s because leadership in software is rare and vanishing.
That’s the real problem but it’s too broad. More specifically, in the absence of accountability developers will do whatever the fuck they want. If you want better performing software you have to enforce performance metrics as a delivery target.
Most shops are just happy that any product ships at all, which is a shockingly low bar of acceptance. Why? Because in the absence of accountability developers will bitch and cry about how hard life is when any performance target is set of any kind. Accountability requires enforcement and liability.
Normally, in software, leadership is intentionally absent because the goal is to maximize ROI by deliberately not training staff and maximize the frequency of hiring/firing with the lowest possible cost friction. In that essence software developers are overpriced commodities in a process of manufacturing. Unfortunately, the result is a shitty product that nobody cares about.
1. Be a manager. You are not there to be their friend. You are there because they are horrible and their leadership needs you to clean up the trash. If you are not there as some form of management with a title and ownership you will quickly become their bitch, which leads to my second learning.
2. Don't get sidelined. As an outsider operating under contract the problem people want you gone but cannot remove you. Their best weapon is to sideline you. If they cannot own you they will ignore you. They will rearrange their meeting schedules and ensure you are not invited. They will create and release prototypes and delivery plans without your involvement. They will write reports and opinions to their management with all kinds of complaints and fictions and you have nothing because you are out of the game.