4 ms·
As someone that was almost entirely self-taught (started as an EE -also heavily self-taught), I’ve looked up many, many noses. One of the manifestations, is tha
by ChrisMarshallNY 6y ago
As someone that was almost entirely self-taught (started as an EE -also heavily self-taught), I’ve looked up many, many noses. One of the manifestations, is that I often don’t know the “official” name of a pattern or the “standard” way to do something, despite being quite good at it.
So I don’t do things the way everyone else does it, and I often fail to deliver or comprehend industry jargon.
But I have been shipping software for my entire adult life. I have an extensive open-source portfolio of extremely well-executed projects that anyone can clone, build and incorporate into a shipping project without worrying about quality or performance. I have had to deliver the goods -in public, and under a microscope- since I’ve started.
I’m highly disciplined, and have been working on large, heterogeneous teams, my entire career. These days, I work alone, or in small teams. Not by choice. Working for a Japanese corporation for 27 years, means that I am very used to hard taskmasters. I’ve had my feelings hurt more often than many.
So I’m used to backing up my rhetoric with deliverables, and watching those deliverables get inspected, criticized, rejected, and improved. It’s made me take Quality rather seriously. It’s also made me quite aware of schedules and deliverables.
Q. C. D.
I’m not particularly competitive, and don’t especially care whether or not I’m “better” than anyone else. I’m used to being the dumbest person in the room (I spent most of my career, working with some of the best engineers and scientists in the industry).
So I work well in teams, know how to bite my tongue, and listen.
Every single day -every single day- I start the day with some scary, insurmountable issue that needs to be solved, or the whole project goes into the bin; and I solve it -often in an unintuitive manner.
So I’m fairly good at solving problems. I’ve been doing it since I was 21, and trained as an electronic RF tech.
I also have dozens of articles, sites, and documentation that I’ve personally written; often going into great detail about how I architect, troubleshoot, test, configure and release. I tend to write in the vernacular, which also means I come across as plebeian.
So I’m pretty much an “open book,” and I’m fairly decent at writing in an approachable, accessible, entertaining manner, as well as coding.
I’d have been happy to have had a more formal introduction to things, but that was not in the cards.
Also, since I’m constantly in “ship mode,” I have to stay focused on practicum, as opposed to theory and exploration. That slows down learning some of the cooler, more esoteric things.
Nevertheless, every day is a new adventure, and I am still learning new stuff, regularly. I feel as if my experience helps me to establish a context that makes learning easier, faster, and more comprehensive.
There’s a lot to learn, and I have miles to go, before I sleep.
- teddyh 6y ago> I often don’t know the “official” name of a pattern or the “standard” way to do something So what you’re telling us is that you don’t communicate well, or at all, with other people. Other people who will, later, have to maintain your code.
- ChrisMarshallNY 6y agoI saw what you did there. That was cute. Hey, here’s an idea…why don’t you check for yourself? All you need to do, is go to my HN handle. https://news.ycombinator.com/user?id=ChrisMarshallNY https://news.ycombinator.com/user?id=ChrisMarshallNY
- teddyh 6y agoI’d rather hear from your co-workers, or, preferably, the current maintainers of software which you originally wrote.
- ChrisMarshallNY 6y agoWell...you're in luck! My LI profile is full of testimonials from both. Feel free to ask me for references. I'm not looking for a job, but I can probably scare up a couple of folks willing to go on record on my behalf. I would also be happy to send you some very relevant links. You could also order the DSLR interface SDK from my former corporation. One of the APIs is a cross-platform imaging device communication layer I wrote in 1995 (in C). I think they still use it. EDIT: Listen, in all seriousness, I'm a really decent chap, as, I'm sure, are you. I regret that we have begun our relationship on this note, and I will no longer engage you. I scrubbed some of the snark off of this reply.
- teddyh 6y agoI wasn’t meaning to be overly snarky in my original comment, it was also an invitation for you to push back with some references of how you do communicate well with others and your code can be easily be maintained by others. This, I imagine, could be due a few different possibilities. It might be that: 1. You do use common idioms and patters, but you don’t know that you do. Perhaps because you haven’t specifically studied them; you might have just absorbed them by cultural osmosis. 2. You might be good enough at explaining things (and naming things) so that you, like Richard Feynman, can explain the most complex things in common simple terms, even though they are not the industry standard terminology. 3. You always find solutions and algorithms which are so simple to understand that you have never needed anything more complex. 4. You have some other explanation which I can’t think of just now. Instead, what you said was some variation of “my work speaks for itself” and “do your own research”, which does not inspire confidence in your communication abilities.