Clay Tech

"clay-works make things real"

translated from clazytech.com

I answer vague career worries with advice built from my own path

Some time ago, a certain “vague worry” came up in conversation, and I gave my own comments in response. Looking back on it later, I felt the content could be useful more generally, so I’ve reorganized it below. I hope it helps anyone struggling with how to stay motivated about their career. The intended audience is people who:

— — — — — — — — — — — — — — — — — — — — —

Motivation and the drive for technical growth are both matters of individual personal values, so all I can really offer is “this is how I think about it.” I believe it’s good to treat each situation as a “phase” matched to your career plan. Broadly speaking: there may be periods of short-term boring work, or periods of hardship, but cutting those into short phases and building up gradually gets you somewhere you couldn’t have reached in one leap. That’s how I think about it. At the same time, I also think it’s hard to predict or plan too far ahead, so it’s better not to overdo that. I joined a company after graduate school, and in my early twenties I was, like a proper member of a big corporation, essentially an errand boy while studying the basics. I arranged procurement of prototype parts, took waveform data while endlessly swapping candidate components, gathered up datasheets and put them into documents presentable to senior and veteran engineers. Once I learned how to use CAD, I kept building PCBs while doing precision calculations to satisfy the specs and changes my seniors had decided on, then measuring waveforms again. In terms of raw development ability, I was probably frighteningly behind many engineers of the same age who’d graduated from technical colleges or had robotics competition experience. But I treated this whole period purely as “study.” If you ask whether it was fun or not fun, I think it was fun. I’d calculate for myself why a part value a senior had placed came out to that particular number and go ask about it, I’d work as the hands and feet of a veteran EMC master, and late at night at an outdoor test site (back then, 10-meter radio measurement sites existed only in shacks deep in the mountains!) the two of us alone would have him kindly teach me the secret sauce (laughs). In meetings, sitting next to my seniors, I learned the company’s overall development flow and how to deal with various vendors. In my late twenties, I went independent. I made sure to think through and design everything on my own initiative for everything I did. Because of that I had a terrible time more than once, and my working hours were the ultimate black-company level, but I don’t think I could have gained confidence in my own technical skill without that period of struggling and nearly dying over and over. (This would take too long to go into here, so I’ll save it for another time.) What I’m grateful for here is that an environment existed at all that permitted that kind of stance. My senior from my OJT days happened to be moving into a department head position right around then, and he pulled me into that department. Things went very smoothly because of that string of coincidences. But what if such an environment hadn’t come together? I imagine there would have come a time for some kind of action — to put it in template form:


Originally published in Japanese at https://clazytech.com/2020/02/322/. Translated with LLM assistance and reviewed before publication.