Hardware will never solve for poorly written software by people who don't know what they are doing. This isn't a technology failure. It's a leadership failure.
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.
Hardware will never solve for poorly written software by people who don't know what they are doing. This isn't a technology failure. It's a leadership failure.
As a software developer this is quite nebulous. The bank protects its reputation by prioritizing risk analysis and ethics first in all its internal decisions. As an industry these qualities do not exist in any professional capacity in software. In software, just like in absolutely every employer, we do whatever we want so long as it eases hiring, everything else be damned.
You can tell difference between focus on the product and focus on yourself with metrics and how readily people are eager to ignore numbers using excuses from poorly formed reasoning reflective of a more honest intent.
The primary problem is that nobody knows what quality looks like. As a result everything is extremely beginner, based on the framework flavor of the moment, and then qualified against leet code nonsense or use of a million different tools. If that is the path you were taking the failure is predictable as the desired target is somebody too immature for writing a product and you not understanding why or caring for the difference.
You, as the hiring manager of the startup have to overcome biases if you want to be successful. Frontend stuff is still software. Treat it as such and look for maturity first before quibbling over technical minutiae. Can the candidate write software? Can they even write at all? Only then evaluate if they have frontend skills.
Only once your startup gets bigger and revenue is both certain and predictable can you relax and hiring the more commonly available immature developers.
2. Writing takes practice. Ignoring this due to any bias is a case for institutionalizing ignorance. At my current employer I see much better writing coming out of India from non-native speakers/writers.
I hate writing about past and current projects in the corporate world where it feels like you own three lines of code in a project of 10 million lines that could probably be refactored to 2000 lines. Instead I describe my work history in terms of responsibility instead of technology.
I showcase my personal projects on my resume but nobody cares. They only seem interested in employment history, which is stupid frustrating when you write 10x more code outside of work and your work work feels extremely entry level.
I just recently found a solution to this: a section of the resume dedicated to recent achievements. There I can mention my accepted pull requests to major OSS projects, how I am a director level manager in my part time job, major technical problems I have solved. All these gems already existed on the resume, but were ignored because they are in the corporate employment history. Now, suddenly people find my resume excited.
I should add in bold red letters at the bottom (for clarity): No experience writing ReactJS.
I have seen a lot of people try this and fail because they aren’t building a personalized kit, they are putting together popular dependencies. That is radically different.
When you build your own kit it is tiny and extremely portable. You dig into the nuts and bolts to see what works and what plays well together. Since it’s all your personal preferences you maximize on productivity every time you use it. The best part is that you only have to build it once. Then after it’s a few hours of maintenance every six months as your requirements and preferences evolve.
Fortunately, I have a part time director level job as a soldier for my backup plan.
I am passionate about this, because decentralization is the most liberating online experience. Share anything, in any way, to anybody of your choosing without third party restrictions, their privacy violations, and no weaponizing of your data/content for any purpose.
Apparently not. A few seconds is a really big deal, but that is just download time while you are also clearly not accounting for execution time. Caching code will not save on execution time.
Its not CPU. Its bad software written by people who are poorly trained and have no leadership.
Do you really need 10mb of JavaScript and 10 seconds of load time to dynamically put a few lines of text on the screen? Yes, absolutely you do, because people don't know how to do it efficiently. This is a people problem, and not a technology problem. Hardware does not solve that problem. The actual technology is actually insane fast. As a counterpoint my personal app loads an OS GUI with state restoration using 2mb of JS code (unminified) in about 150ms.
Over sharing, or the idea of broadcasting details about my life to strangers on the internet is also something I completely don't understand.
You do care or you wouldn't be arguing with me and sounding emotional.
I suspect the goal is to widen candidate availability to the maximum, cast the widest net. I find this odd because compensation is now absurd competence, experience, and product quality be damned.
The only distinction that matters in what you are arguing is level of education. Again, this is about a very basic command of the written word and at the same the subject here is academic research. Your comment is suggesting a colloquialism as an excuse for poor writing when actually colloquialisms have no business in academic writing.
https://en.wikipedia.org/wiki/Colloquialism
Like I said before I can also understand why these concepts, even though they are incredibly basic, are so absolutely foreign to a community of software developers that don't frequently write or read academic research.
It actually does. The primary difference is first-person pronoun use versus reliance upon external factors, such as evidence of any kind. That shift indicates a trend towards narcissistic thinking and possibly isolation.
I would say your scenario is absolutely an ethical violation called a conflict of interest.
https://compliance.ucf.edu/understanding-conflict-of-interes...
In some cases a failure to disclose a conflict could be illegal, as in a form of fraud.