A Meditation on the Art of Not Trying • Hacker News Board

Re: A Meditation on the Art of Not Trying

#31

Post by curiously » Sat, Dec 20, 2014, 8:54 PM UTC

RangerScience wrote: post #29

So about two months ago, on about my two-year anniversary with the company, I switched from "Software Engineer" to "Solution Architect" (aka "Biz Dev Engineer"). It means that I now go to a lot of meetings (frequently with clients), where people draw on my knowledge of how our things work, and build a few things on the side. Mostly marketing material. It's a crazy different experience from actually writing the code,…

im a software engineer and looking to make the same switch do you have any advice on how you got there? another role im thinking of is sales.

Re: A Meditation on the Art of Not Trying

#32

Post by curiously » Sat, Dec 20, 2014, 8:57 PM UTC

I have a great difficulty understanding this article. How can one accomplish anything without trying?

Believe me I spent years smoking weed, being myself and trying to build something. It didn't work.

Now I am told to not try? Or does this actually mean to just relax but not a be an idiot?

Paradoxes infuriate me.

Re: A Meditation on the Art of Not Trying

#33

Post by anon4 » Sat, Dec 20, 2014, 9:05 PM UTC

fsloth wrote: post #8

Is this about Analysis paralysis vs. learning by doing? From what I understand of asian philosophy, I think the dichotomy between he Confucean and Taoist value systems is a very good mental tool - the former stresses academic learning and analysis while the latter strives for simplicity and doing what you can, right now, with the knowledge and tools you have. To draw a caricature: The confucean systems hold the burea…

I think you can actually unify both. That is, have both a system that lasts for decades and have people move with spontaneity. The key is to disentangle the system which dictates how things fit together from people's personal lives. The system needs specific roles filled, but the people filling them don't have to be the roles themselves and further, the system itself must evolve, driven by the changes in the people that are in it.

Re: A Meditation on the Art of Not Trying

#34

Post by RangerScience » Sat, Dec 20, 2014, 10:57 PM UTC

curiously wrote: post #31

RangerScience wrote: post #29

So about two months ago, on about my two-year anniversary with the company, I switched from "Software Engineer" to "Solution Architect" (aka "Biz Dev Engineer"). It means that I now go to a lot of meetings (frequently with clients), where people draw on my knowledge of how our things work, and build a few things on the side. Mostly marketing material. It's a crazy different experience from actually writing the code,…

im a software engineer and looking to make the same switch do you have any advice on how you got there? another role im thinking of is sales.

I started by pursing "sales engineer", but then someone said the magic words "solutions architect" and it went from there.

Find the person who would be your boss if you switched, and start talking to them about it?

I don't think I have any other relevant anecdotes, my situation was pretty weird.

Re: A Meditation on the Art of Not Trying

#35

Post by curiously » Sat, Dec 20, 2014, 11:02 PM UTC

RangerScience wrote: post #34

curiously wrote: post #31

Earlier quoted context omitted.

im a software engineer and looking to make the same switch do you have any advice on how you got there? another role im thinking of is sales.

I started by pursing "sales engineer", but then someone said the magic words "solutions architect" and it went from there. Find the person who would be your boss if you switched, and start talking to them about it? I don't think I have any other relevant anecdotes, my situation was pretty weird.

what is the actual range of experience required to do the job of a solutions engineer?