28 karma · joined June 23, 2018
no piece of hardware or software is safe from evil deeds of people building them.
Then you seemed to be surprised by the issues, again showing you lacked the experience of a senior. I feel you got good guidance but it feels it was not well received.
The away team experience also felt a bit juniory. Your requests we not priotorized high enough but you didn’t find the tools or means to go around it. Understanding their needs and life in general would be an indication of seniority.
Finally, I think it takes at least a year to see how you are able to cope and progress. It takes time and effort to make any changes in a huge corporation.
In the end, I think that you would not have enjoyed yourself working in that environment so you made the right call. It takes certain character traits to be able to enjoy navigating and gaming such corporate culture.
Source: ex enterpreneur with two decades of experience, atm employed in a >100k employee corporation and loving it.
| given the fact that I wasn’t too efficient with Java (it was not the primary tool in my past experience)
Maybe because his 10 years didn’t give him the relevant knowledge? Also, his attitudes sends a clear ”I’m a junior” message, so SDE1 might have been right call.
if the answer is no, then I don’t think that even feedback would help in the original problem..
I guess the same logic applies directly to self-driving cars as well..
Personally, I’d refuse to implement self-driving vehicle without at least a ”backup LIDAR” to check vision system results. Otherwise you are forced to assume stuff like ”things at stand still are either above the road, beside it, or just shadows”, causing crashes when there is suddenly a stopped car in front of you. (If you didn’t do that assumption, you would be dodging shadows and other clutter..)
[source: I’ve been researching vision algorithms in a related field.]
edit: to add, those people already have the tools they need to automate the things they want. They just lack the will to learn to use the tools.
edit2: to continue the analogy. I can drill a hole to a wall but if I need to dig a big hole, I can either learn to drive a tractor shovel or hire a professional to do it. But I’m not complaining why tractors are so hard to drive..
If some business owner finds a way to monetize such tools, nerds will be happy to implement. Just as those do-it-yourself fix-your-home books and tools have been monetized and implemented.
Building a proper house is so much more that just piling rocks mixed with mortar. You have to take into account the ground composition, moisture, light, ventilation, red tape, usability, safety, etc. In other words: it takes a huge set of skill. You can use advanced tools, like a tractor shovel for digging the base but that requires even more skill.
We just have to accept that doing complex stuff requires lots of training to do it properly. The more advanced tools you use, the more specific training you need but the more complex stuff you can build in shorter time.
As for programming. Abstract thinking and clear, explicit communication of ideas is not trivial to automate. This is problem even between two persons (just think about trying to decipher what your sales person or customer actually wants), let alone between a human and a machine. It’s a form of art, not some mechanical process you automate using an array of boxes.