This is not a politically correct thing to say but there is a class of neurodiverse software developers who display these characteristics and I suspect the author belongs to this group.
You have to be able to pick your battles. Sometimes people are in the wrong teams. Sometimes they are just assholes who think they are always right. Too often the "right thing" is subjective.
A brief exercise in shipping an MVP and seeing if it gets traction before refining the feature set =). Thanks for reading my ramblings despite the lack of proofreading hopefully its a bit better for others now.
What came to my mind when reading the unedited copy is that you are confusing MVP with prototype. An effective MVP is something that does relatively very few things but that does them well or very well. Otherwise your churning will be huge. In other words, I read your post completely but it was somewhat painful because the copy was not polished for clarity, so I doubt I read a second one. I churned. To build effective MVPs you need to keep an eye on quality. Do fewer things that work flawlessly will have much more impact than throwing a bunch of things to the wall. You need to make a culture change and overweight quality. And I also recommend B2B if you happen to be trying B2C.
"I didn't have time to write a short letter, so I wrote a long one instead".
As a "tech guy", I never understood the notion of MVPs. Sure, start small makes sense, but delivering something half baked just demonstrates one doesn't care enough for their readers/customers. Why would anyone like to put himself in such a position?
"Google’s CEO Sundar Pichai (who believes AI is “more profound than electricity or fire”) has emphasized that Google is an “AI-first” company, with the company seeking to implement machine learning in nearly everything do"
Not sure if a part of your post got cut off? As framed, it seems rather inflammatory without much direction or practical addition to the conversation. Perhaps I'm missing something.
Nope, nothing got cut. My post stands as I wrote it. It is not ad-hominem and not what-aboutery. It is very much a reasonable question to ask what they use their much-touted AI on and how this relates to the well documented privacy concerns around Google.
IMO they are clearly betting (parts of) the farm on this as can be seen by the (often) ridiculous results many of us have witnessed in both search results quality and ad matching quality.
The best idea is to not use their services. Switch from Windows to Linux, de-google and if you must use Android keep the data on your phone to a minimum.
Questions about tests. I have found consistently that when an interviewer does not know what the test coverage of their codebase is, more likely than not they don't care about such trivialities.
No matter how respectable the company might look on the outside, the codebase is an incorrigible mess built by cowboys and they will expect you to maintain it.
I'm going to just say that making a codebase testable increases the complexity by a couple of orders of magnitude. Certainly it's great for some things. For other things it's a net negative.
Frankly, reminds me of Michael O'Church
reply