Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> 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.



I 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


I’d rather hear from your co-workers, or, preferably, the current maintainers of software which you originally wrote.


Well...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.


I 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.


OK. I know I said I wouldn't engage more.

I lied. I liked your response.

What I wrote was completely self-expository. It really is who I am, and I'm used to writing that way. It was not a challenge, and it was not an attack on anything (I can easily do "attack" -I'm an old UseNet troll).

As I mentioned above (below?), it saddens me that people see self-exposition from others as weakness and a vector for attack. That's one of the reasons that I'm no longer interested in working for anyone else in this industry, and why I no longer want to be a manager.

Things are nasty these days. Hyper-competitive. We can't just be good at something. We need to be better than someone else.

We can't just be enthusiastic. We need to be combative. Everything is a gladiatorial contest. Thumbs up/down.

After leaving that silo I'd been in for 27 years, I started looking for work, and rapidly discovered what this industry I love has become.

I don't really want to play in the cesspool, but I love to code.

I guess I am "taking my toys and going home," but I am very, very fortunate in being able to do so.

I'm working on a fairly ambitious project, right now, that will (I hope) help out a lot of folks. I have some prior art in the area. I'm working for a non-profit, for free.

And loving it.


This right here. We often talk about "Communication skills". This isn't separable from "being able to describe a problem or solution using standard terminology".

It's no less important to know what common things are called, than it is to know how common things work.

There is no brighter red flag to a than people who just "gets things done" or "solve problems in unorthodox ways", so a candidate who describes themselves as a problem solver that might not know all the "words" for it is to me a big red flag. This isn't gatekeeping or saying everyone needs a CS degree to be a decent developer. Terminology is a trivial addition to the skillset and ignoring it just means one doesn't care about communication.


...and then, there's spending 27 years, working for a conservative Japanese corporation, where they don't know the jargon (but are seriously good engineers). I learned to make things fairly clear, without jargon, and deliver very maintainable code (I'd have been fired, otherwise).

Listen, I understand that researching people before we insult them is passé, but I'm a really good co-worker. I wrote the above in a manner that was all focused on me, not anyone else. I am sad that you saw it as an opportunity to attack.

Maybe we would not get along IRL, and that's fine (but sad). I've spent my entire adult life, working with some of the most difficult folks on Earth (not in the tech industry). I have learned that we all have a story, and we all have value.

If the only way that we can measure our personal worth is to compare it favorably against others, I can't help, there, except to say that it didn't work for me.

YMMV




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: