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.
The valley has amazing job opportunities for software developers and incredible weather. Transportation there, thinking BART, sounds incredible too.
Houses there used to be 8-12x more than where I live but are now more like 6-7x more and everything costs more there such as food, fuel, taxes, utilities, and so forth. The valley also has a subculture that many other Americans find a bit politically extreme with strange local politics practiced by elected authorities.
By maturity window I mean a candidate is most ideal for this line of work if they fall within a certain segment of a bell curve, a Goldilocks zone of not too great and not too bad. This maturity window is dictated by hiring preferences, work culture, and product averages, but not by technology.
For example the industry is approaching a point where developers are not employable without going all in on React framework even if a developer can ship superior products in a fraction of the time without the framework. A decade ago jQuery held this position. The business objective appears to allow a wider pool of applicant availability where many such applicants would be unqualified. This eases hiring for the employer and allows access to high paying work for people who would otherwise be grossly inadequate. That accounts for the maturity window on the low end.
Reliance on nonstandard or supplemental external tools to define a job creates artificial averages in both product and high end labor. A developer can only be as productive as the framework allows. The product can only execute as fast as the framework allows. It also caps innovation in that a high end developer might otherwise be capable of offering innovative solutions is now limited to the artificial constraints of the framework.
This scenario creates an ethical dilemma for all parties. When developers define their capabilities and employment by use of a tool or framework what happens when that tool goes away? Does the developer achieve functional obsolescence? This primes and incentivizes developers to preference their self interest above that of the consuming user as necessary to remain employable. It also primes employers to target applicants who lack the maturity to appreciate this.
Sometimes poor development environments are a reflection of culture. If that is the case only a leadership solution will set things on a more productive direction. In cases where leadership is present and engaged a poor development environment is the result of missing technical guidance, which is likely due to a disconnect between a plan and actual implementation reinforced by developer driven decisions. Developers should never drive the direction of a product unless they are stakeholders with liability.
Just to be clear I am not a software leader. I am just an individual contributor, so take this with a grain of salt. I am a military officer though, in a secondary line of work, with director level responsibility and a large staff.
* Be clear about requirements. If the requirements aren’t clear push back before doing any work.
* If you are working defects expect reproduction steps, a test location, defect state, and desired state. If this isn’t clear push back on it.
* if you cannot deliver code, because the work environment is shit, then deliver better documentation.
The problems I encounter at my work is that just about every is slow. Those who aren’t appear to hoard product knowledge and are really shitty at communicating. I really want to say that is intentional behavior but I just think it’s actually a mix of shitty code, fear of writing, and aggressive posturing by people who want attention compared to everyone else. The key failure here is that the employer rewards hard work without quality checks.
In more than 80% of cases accessibility is free if you know what you are doing. The best business case there is a competence filter on hiring front end developers.
JUL 2012 - $147k
DEC 2015 - $202k
AUG 2017 - $223k
OCT 2018 - $251k
NOV 2019 - $250k
MAR 2021 - $280k
APR 2021 - $308k
JAN 2022 - $352k
I do not live in Austin though. Too pricey with worse traffic, as if that’s even possible. Austin also has strange local politics.Those who are concerned about falling into the trap of the McNamara Fallacy shouldn’t abandon quantitative measurements and metrics.
A key example is Moneyball: https://en.m.wikipedia.org/wiki/Moneyball
In my line of work, JavaScript, people will intentionally ignore data that challenges their favored approach. Measuring things is important, but all these examples illustrate that measures are irrelevant when ethics are absent, which is worse than measures applied too narrowly as in the McNamara Fallacy.
1. Wake up ridiculous early. Let’s say 5am (not that ridiculous).
2. Force yourself out of bed with a purpose. If necessary provide external motivation by priming pets or children to demand things of you at this time, be somewhere such a morning run with a group.
3. After the priming event do not go back to bed. Instead get ready for the day by showering, getting dressed, eating breakfast. Personally I put these on hold as I am already thinking about writing, a software enhancement, or where I last left off on some new game.
4. Start your daily routine whether that is driving to work or logging in from a home office.
5. Become engaged in the priorities of the day.
The trick is to have purpose and remain constantly engaged with drugs like caffeine. You will get drowsy as mind fades from purpose into a relaxed steady state, but by that point you are well out of early morning. At that point you can have caffeine if you need it.
Remain engaged for the rest of the day. You will become tired by early evening unless you are the kind of person that needs very little sleep. I tend to get by on 4.5 to 5.5 hours myself.
The worst thing you can do in this process is consume alcohol.
Institutionalized quality would include:
* Uniform minimum accepted standards of practice.
* Uniform foundations of minimum accepted product quality.
* Uniform accepted measures and metrics.
* Formal training dedicated to standards and software as a platform, not tools.
* Credentials to certify standards of practice and conformance to ethics therein.
Instead children are left to drive the bus and cry about how hard life is. Anytime this subject comes up there appears to be no adults in the room.
Why? I think the unspoken alternative to boring is gross negligent incompetence.
It really doesn’t have to be that way. The web is 30 years old, JavaScript is 25 years old, and the mature DOM is 23 years old. Surely by now somebody can figure out how to dynamically add text to the screen with less than 10mb of JS taking less than 10 seconds to execute.
As a counter point I have written an OS GUI that is 2mb unminified and loads in the browser in about 55ms (give or take 5ms) including full state restoration. That’s pretty fast. Looking at various benchmarks JavaScript is now executing as fast as Java in many micro-benchmarks.
If this stuff is really that fast why we do we tolerate such incompetence writing frontend code? It’s like incompetence is built in by default as the standard expectation and everybody hires accordingly.
* Train for a 10k run and then train for a half marathon.
* Join a local charity and contribute towards your community.
* Join the military and learn new skills while traveling the world.
* Build something with your hands such as modeling or wood working.
* Write. Writing is a skill so no matter what you are writing it will take some practice.
* Get a pet to raise and cherish it. My cats and dogs are among my closest life companions.
* Go back to school and work on a graduate degree.
If you want decentralization look at WebRTC. https://webrtc.org/
If you want crypto you have to guess at what resources are valid.
Just keep in mind the only commonality in crypto is blockchain, which is a distributed form of third party storage. Crypto will not get you decentralization.
As a JavaScript developer everybody wants to tell me how it’s done, what the right way is, and so forth. It’s not worth arguing over because the most incompetent developers tend to be the most vocal ones.
I have been writing JavaScript full time for almost 15 years and most corporate JavaScript I see is complete garbage. How do you know what excellent code is? Numbers. Code size, execution time, maintenance time, defect resolution time, test automation capabilities, new feature delivery time, and so forth. For example if your app takes 4 seconds to load and mine takes 50ms I will just assume I am less wrong, but you can’t advocate for that because will cry about code style and frameworks and other bullshit. So silently I write my personal project.
The only problem here is an employer claiming ownership of a personal project, assuming the personal project isn’t interfering with employee product delivery and isn’t violating employer security policies.
My solution to this is dual employment. My secondary employer has trouble differentiating work time from personal time so they end up with the most liberal IP assignment policies I have ever seen. Everybody, corporate IP attorneys, know this.
So, unless it’s making money or an employer wants to lay down a provision patent they won’t fight you on it. They are fully aware the alternatives are moving to another company or to stop innovating. As a result most employers with silently bless the personal projects even on company time. They won’t bless these efforts directly because personal projects on company time or property are ethical violations that legally compel the employer to take ownership and shut it down. That is the last thing anybody wants.