News for hackers. Stuff that matters.
Re:Drunk Post: Things I've Learned as a Sr Engineer by daenz on Sunday May 30, 2021 @11:28AM (#27333918)
>Don't meet your heroes. I paid 5k to take a course by one of my heroes. He's a brilliant man, but at the end of it I realized that he's making it up as he goes along like the rest of us.

I thought they were going to go the direction of "he's an asshole" and was ready to accept that, but this particular criticism is actually disturbing. People with strong visions can often appear to be "making it up as they go along," when really they are just subpar communicators.

Short story, I am helping my current company switch from a monolith to service-oriented architecture, and in the process have built a framework for spinning up new fully-deployable services from scratch that gets engineers 90% of the way there (minus the business logic). I have a strong vision for how it works and had a dozen-page RFC accepted by the engineering team for it. Yet there are engineers who think I am making it up as I go (I have been asked this indirectly), without any vision guiding the pieces into place. I have chalked up this feedback to me needing to improve my communication of the vision.

So the post's response of "I realized that he's making it up as he goes along like the rest of us" is disturbing because it makes me realize just how difficult communicating a vision is... if this hero that the poster paid $5k to go see can't even convince one of their fans, what chance do normal people like you and I have of convincing people that we're not making it up as we go?

>EDIT: I realize that I am posting under the assumption that the person's hero does in fact know what he's doing. If he truly is making it up as he goes, the above doesn't apply.

Re:Drunk Post: Things I've Learned as a Sr Engineer by swader999 on Sunday May 30, 2021 @11:40AM (#27333996)
What is wrong with making it up as you go? I mean everything I've ever built I had a notion of what I was doing but most of the real work was in the details. Anyone could say I was making it up as I go. I'd be like yeah, if I knew completely how to do it, I'd already be finished it.

Then there's the times where you think you know exactly what you're doing and after going down a road you realize it's the wrong way. Failing to learn and see the signs and make the embarrassing declaration that you got lost and need to turn around is never good. But some people just keep driving. It's hard though when there's a big line of cars behind you that think you actually know where you are headed.

Re:Drunk Post: Things I've Learned as a Sr Engineer by daenz on Sunday May 30, 2021 @11:47AM (#27334052)
Nothing wrong with making it up as you go, and I didn't mean to sound like I was knocking it, if I did. Sometimes everyone fumbles around trying to find solutions that work...it's a totally valid way to approach some problems.

Sometimes it's a hybrid of knowing what you are doing but not knowing the implementation specifics. You know you need to connect high-level pieces A, B, and C with specific constraints, but it won't be until you get into the low-level implementation that you'll know if it is indeed possible. I think that's an example of both having a vision and also improvising as you go.

I am concerned about how to effectively communicate visions to people, because it gets everyone rowing in the same direction. If nobody thinks that you have a vision, when you do, there is no reason they should choose your direction vs just do their own thing.

Re:Drunk Post: Things I've Learned as a Sr Engineer by swader999 on Sunday May 30, 2021 @12:25PM (#27334326)
Ok this is helpful. If people are doing their own thing and not following the established, agreed on (or even dictated) way or vision, then you need to figure out why if you are the lead.

Maybe it is communication related. Does everyone know that this is the way they should do something? But they still don't? Have you created docs and edicts around these areas? Have you been assertive in code reviews? Have you been proactive and requested design sessions before a lot of work was done?

Has a decision been formally communicated? I see this step not happening enough, people are hesitant to be authoritative after a discussion on architectural concerns. If you are the lead, that needs to happen.

Most of the time it's simply a case of them not knowing how to do it. People are afraid to show their lack of skill and knowledge and ask for help. They get deadline pressure and deliver their default way.

Have you provided a feature or cut through the system that shows this vision for people to follow? Maybe example code, resources on the web that go very deep into the ideas and tactics? Have you paired with them to help them get started or get over obstacles. Perhaps pair your most senior person with juniors for a while to get them on the same page and capable with this vision.

Re:Drunk Post: Things I've Learned as a Sr Engineer by mikepurvis on Sunday May 30, 2021 @01:52PM (#27335037)
Using a phrase like "fumbles around" still sounds like you're placing it on a lower rung, whereas I would say that basically everything I've ever done has been an iterative, collaborative process, including in situations where I'm highly confident of both the problem domain and technology choices. There are always going to be new discoveries made during implementation, and you can't have a written-in-stone design doc that prevents anyone on the team suggesting a refinement.

For myself as an opinionated person in a devops role, the vision that I try to communicate to my colleagues is mostly broad principles like configuration as code, helping people help themselves, consolidation of systems, and then some more pointed specifics like don't touch prod, don't make changes without a consensus, start by understanding why it's the way it is before changing it, etc.

Re:Drunk Post: Things I've Learned as a Sr Engineer by marcinzm on Sunday May 30, 2021 @04:09PM (#27336279)
>I am concerned about how to effectively communicate visions to people, because it gets everyone rowing in the same direction. If nobody thinks that you have a vision, when you do, there is no reason they should choose your direction vs just do their own thing.

I used to have visions. Now I have collaborative design discussions driven by some starting designs. I found that if people don't contribute to the overall design then they have little impetus to actually understand it. This tends to lead to a better design and a more engaged team so a win on all counts.

Re:Drunk Post: Things I've Learned as a Sr Engineer by swader999 on Monday May 31, 2021 @07:39AM (#27342975)
They are far less rigid at this stage as they haven't invested a lot of coding time.
Re:Drunk Post: Things I've Learned as a Sr Engineer by aiisjustanif on Monday May 31, 2021 @12:23AM (#27340101)
100% this.
Re:Drunk Post: Things I've Learned as a Sr Engineer by jtolmar on Sunday May 30, 2021 @11:53PM (#27339890)
> What is wrong with making it up as you go?

Nothing if you're good at it. But if you're hoping to learn something from someone, it is pretty disappointing. How to make it up as you go along is far less teachable.

Re:Drunk Post: Things I've Learned as a Sr Engineer by the-pigeon on Sunday May 30, 2021 @11:37AM (#27333983)
It really depends.

I take this really just to mean "everyone has faults".

People often idealize heroes and think of them as beyond human. If you do that and met your hero then your illusion will often be shattered. But the problem is just that you were putting them on an unreasonable pedestal.

Of course some people are frauds and some people have no idea what they are doing but manage to make people think they do. But I didn't read this as being one of those situations. Just someone they saw as beyond human being only human.

Re:Drunk Post: Things I've Learned as a Sr Engineer by bitexploder on Sunday May 30, 2021 @11:39AM (#27333993)
I like the phrase “kill your heroes”. Not literally, of course. But in your mind. They are just flawed people like everyone else that happen to have been mythologized. Learning more about your heroes often leads to disappointment.
Re:Drunk Post: Things I've Learned as a Sr Engineer by vlunkr on Sunday May 30, 2021 @11:52AM (#27334081)
I've recently found a podcast called "your favorite band sucks" that's along these lines. They have real criticisms of popular bands, but it's also a bit tounge-in-cheek. It's a nice contrast to the typical worship of rock bands. I think it's healthy to be able to enjoy something, or be inspired by someone, without buying into the mythology.
Re:Drunk Post: Things I've Learned as a Sr Engineer by tester756 on Sunday May 30, 2021 @03:27PM (#27335898)
I have different take on this

I "know" guy who's conference speaker, so he knows other conference speakers, drinks vodka with them and so on.

He says there's significant amount of bullshit aka things that work nice on slides, things that only work cool in theory, but in practice they arent as great

I think that's what OP meant

Re:Drunk Post: Things I've Learned as a Sr Engineer by booleandilemma on Sunday May 30, 2021 @11:33AM (#27333954)
A common meme I've seen recently is "no one knows what they're doing".

I think people like to believe this because it helps them cope with impostor syndrome, or maybe they think it puts them on even ground with people who do in fact know what they're doing.

Re:Drunk Post: Things I've Learned as a Sr Engineer by mortenjorck on Sunday May 30, 2021 @11:57AM (#27334115)
My model for people who "know what they're doing" is that they tend to have a well-organized hierarchy of rules. At the base are principles; at the top are opinions.

The foundation tends to be pretty simple, deeply held, and unchanging, while the higher levels are increasingly fluid and specialized. The higher you get on this stack, the more "making it up as you go along" it becomes, but every improvised part is perched on something more stable.

They key to "knowing what you're doing" is organizing this hierarchy well, having the right supports in place to successfully guide improvisation and course-correction while steadily fortifying the foundation.

Re:Drunk Post: Things I've Learned as a Sr Engineer by WJW on Sunday May 30, 2021 @11:47AM (#27334054)
It's clearly not true in all circumstances. You can bet that an airline pilot has a very clear idea of what they are doing, and so will your dentist. Closer to home there are plenty of sub-fields in software where I'd be completely lost but when (say) we have to add a new endpoint to the webservice I work with, I absolutely don't have to make it up as I go along.

Your assessment of why people like to believe this seems spot on.

Re:Drunk Post: Things I've Learned as a Sr Engineer by andreilys on Sunday May 30, 2021 @11:54AM (#27334097)
Even worst is the meme that “programming is just copy+pasting from stack overflow”
Re:Drunk Post: Things I've Learned as a Sr Engineer by user_50123890 on Sunday May 30, 2021 @01:01PM (#27334624)
Because good senior programmers are rare (as can be observed if you post a job listing).

Most of this stuff comes from students / junior developers, where yes, they probably visit stack overflow every 20 minutes

Re:Drunk Post: Things I've Learned as a Sr Engineer by MikeDelta on Sunday May 30, 2021 @01:12PM (#27334725)
They should try programming on an airplane or without internet connection. For some the productivity drops to zero without stack overflow.
Re:Drunk Post: Things I've Learned as a Sr Engineer by hutzlibu on Sunday May 30, 2021 @06:22PM (#27337460)
"For some the productivity drops to zero without stack overflow."

And it is bad to be a newb? And even for experienced devs to go to stackoverflow regulary ... isn't it productive, to not always reinvent the wheel?

I can solve allmost everything on my own. But if I have a new problem, I assume someone else already had - I would be stupid, to figure it out on my own, when I could get a working solution in 5 min googling.

But I actually programm without internet connection most of the time, as I like being outside, away from noise (and wifi)

Re:Drunk Post: Things I've Learned as a Sr Engineer by javagram on Sunday May 30, 2021 @07:53PM (#27338235)
The issue does arise when you aren’t able to understand the problem space enough to realize that what you copied from stack overflow has a mistake or doesn’t fit the requirement you need (e.g. perhaps it doesn’t match your error handling architecture or so on).

That said, stack overflow can be a great source and I’ve written plenty of code with a comment pointing to a SO link to further explain a pattern or snippet for a future reader.

Re:Drunk Post: Things I've Learned as a Sr Engineer by hutzlibu on Monday May 31, 2021 @02:28AM (#27340880)
"The issue does arise when you aren’t able to understand the problem space enough to realize that what you copied from stack overflow has a mistake or doesn’t fit the requirement you need "

Yeah sure. A stupid programmer will remain a stupid programmer, even if he reaches a certain productivity by living off of stackoverflow ...

Re:Drunk Post: Things I've Learned as a Sr Engineer by MikeDelta on Tuesday June 01, 2021 @06:58AM (#27352774)
There is nothing wrong with copy pasting code from stack overflow.

I do see two kind of people doing that. One group learns from the code in order to become better, and can use it over and over to be more efficient. The other group doesn't care how it works and just wants to have a snippet that works.

The second group usually misses a curiosity, of which the effects show up in many more places than just copy pasting from stack overflow. They also tend to have a flatter learning curve. I don't want to generalize, but in this group you will encounter people who don't care about the difference between a list and a set, or think that code works when it compiles. In both cases the juniors know very little, but one grows and the other one doesn't (or less)

There is space for both in the world, but I prefer the first group in my team.

Re:Drunk Post: Things I've Learned as a Sr Engineer by convolvatron on Sunday May 30, 2021 @05:45PM (#27337161)
i grew up a long time before stack overflow. actually used man pages and read books. there is just _no way_ to program in Rust or Go without access to a search engine and the package libraries.
Re:Drunk Post: Things I've Learned as a Sr Engineer by emidln on Sunday May 30, 2021 @06:18PM (#27337438)
I've done various rust and clojure projects by downloading a lot of git repos ahead of time for reference while on a long-haul flight. This works pretty well, but you need to do a bit of research ahead of time on which libraries you might want access to. This is probably slower, as you have to read source code and think more about the type signatures (rather than looking at some misc example), but if you have 15 hours, what else are you going to do?
Re:Drunk Post: Things I've Learned as a Sr Engineer by sethammons on Monday May 31, 2021 @10:34AM (#27344448)
You can spin up godoc locally and access it locally fyi. Wont help pull in a new package. And you can always drill down into the stdlib implementation right from your editor if you have jump to declaration. I wrote a custom consensus protocol implementation in Go on a flight for work sans wifi.
Re:Drunk Post: Things I've Learned as a Sr Engineer by toss1 on Sunday May 30, 2021 @12:01PM (#27334151)
The criticism may depend on different values of "making it up as you go along", i.e., it may not mean so much "just wing it in ignorance" vs something like "even if you have many answers you don't yet have all of them, and new answers generate new questions exponentially...". So, perhaps less "everyone's ignorant" vs "we're all living in a land of many unknowns". But, yeah, he did find it disillusioning, and maybe is over-generalizing from a one-off experience (in contrast, I've done similar and was nothing but impressed, finding it is extremely valuable to learn from the best in a field).

How do you distinguish between what you do and "making it up as you go along"?

Re:Drunk Post: Things I've Learned as a Sr Engineer by staysaasy on Sunday May 30, 2021 @11:39PM (#27339810)
IME most people will generally appear to be making things up as they go – even if they have significant relevant experience. Every situation is unique, and experience tends to look more like having a list of techniques with varying degrees of expertise, rather than having a playbook for every situation. You have to look for the expertise rather than raw confidence.

In sports terms it would be something like a baseball pitcher being able to throw a great curveball, a great fastball, and an all right slider, and knowing roughly what situations to use them in. There will still be a high degree of randomness and mistakes will be made.

Re:Drunk Post: Things I've Learned as a Sr Engineer by antod on Monday May 31, 2021 @03:27AM (#27341254)
Agreed. What experience and talent gives you are instincts that improve the chances of whatever it is "you're making up as you go" working well.

I would much rather work with people who have a good track record of making it up as they go as opposed to people coming in with a fixed idea of how something should happen and are more likely to misapply whatever lessons led to those views (probably someone elses anyway).

Re:Drunk Post: Things I've Learned as a Sr Engineer by karmakaze on Sunday May 30, 2021 @12:05PM (#27334187)
> built a framework for spinning up new fully-deployable services from scratch that gets engineers 90% of the way there (minus the business logic)

I'm guessing that this was based on first-hand experience building such services and witnessing engineers struggle getting new services up. And not so much that you've had specific training or past experience in developing bootstrapping frameworks. This would be my definition of making it up as you go and is great way to do it. Another way is learning how to make bootstrapping frameworks and applying it wherever you can which doesn't go as well.

Re:Drunk Post: Things I've Learned as a Sr Engineer by dehrmann on Sunday May 30, 2021 @03:02PM (#27335644)
Related thing I'd add: be very careful about taking a dream job; I've seen this happen a few times--it's likely to disappoint. Also dating a minor celebrity crush.
Re:Drunk Post: Things I've Learned as a Sr Engineer by tomnipotent on Sunday May 30, 2021 @10:19PM (#27339304)
In your particular instance, I would have collaborated with a single team to work on converting a single service over to the new framework. Once some success was made, it would be much easier to make traction with other projects and teams. Also, a vision or a plan doesn't mean you're not winging things as you go.
Re:Drunk Post: Things I've Learned as a Sr Engineer by thisismyswamp on Sunday May 30, 2021 @03:33PM (#27335952)
Building a new framework should be way at the bottom of your list of things to consider. If you do, please make it a blackbox. It's tiring how many details one often needs to get into before being able to do something they could have summarized in a sentence the whole time. But this is a general issue!
Re:Drunk Post: Things I've Learned as a Sr Engineer by rwmj on Sunday May 30, 2021 @01:34PM (#27334911)
Also which "hero" is charging 5k for courses and what form does the course take?

(I work at Red Hat, and my programming heroes are also my colleagues.)

Re:Drunk Post: Things I've Learned as a Sr Engineer by tayo42 on Sunday May 30, 2021 @11:58PM (#27339928)
I wonder if it was a course at something like a conference? I think those are expensive. I can't imagine anyone is charging 5k that seems absurd
Re:Drunk Post: Things I've Learned as a Sr Engineer by ww520 on Sunday May 30, 2021 @07:49PM (#27338200)
It just means don't blindly trust the experts.
Re:Drunk Post: Things I've Learned as a Sr Engineer by gher-shyu3i on Sunday May 30, 2021 @01:06PM (#27334666)
The problem is idealizing such people in the first place. Sure, they may have had incredible achievements, but they're humans at the end of the day.