News for hackers. Stuff that matters.

mkanat

Re:Are Ghost Engineers Real? on Monday December 09, 2024 @11:59AM (#42367921)
Hello! I have done this sort of research internally at companies and have coordinated with the world’s leading researchers in developer productivity for a long time.

Myself and every other leading researcher in the field that I have spoken to have serious concerns about this supposed “research.” For example, you can see a post here from Margaret Anne-Storey, who is arguably the world’s leading researcher in developer productivity:

https://www.linkedin.com/posts/margaret-anne-storey-8419462_...

I share her concerns. I have asked Yegor multiple times when he plans to publish his research methodology for review by others and he has not even answered my question. That is, he hasn’t even said “it’s under review and we will publish it by _____.” He’s certainly argued with me about the validity of his results, but suspiciously has not actually published any research methodology as far as I have been able to find.

This is very concerning, because I have worked with this type of data set extensively. I am possibly one of the world’s leading experts in using and analyzing this type of data, and I can tell you that it is fraught with data anomalies of the sort that would easily cause an incorrect result here. For example, you might believe all developers are working in GitHub, but then it turns out the company has 10% of developers contributing to some other source control system. Or one of your GitHub orgs isn’t instrumented correctly. Or some of those people aren’t actually software engineers even though they have a title that _looks_ like that. The list goes on and on, and these are _real_ problems that happen in the data at _every_ company.

Im frankly shocked that the Washington Post or any other credible media organization is publishing this without any verification or background on the validity of the research.

I am fully willing to believe that some engineers don’t do work, or do very little. I’ve seen it. But if you’re going to claim that you did research for a University, with the University’s name on it, I expect things like a published paper, understanding the margin of error on your published numbers, etc. especially in a field that is so prone to errors in the data.

Re:Effective Engineering Productivity on Monday April 10, 2017 @05:46AM (#14077147)
I dunnow. I don't think that finding out what people's problem is and solving it in a way that is real to them is specifically or exclusively the domain of PM or UX.
Re:Effective Engineering Productivity on Monday April 10, 2017 @05:45AM (#14077143)
Maybe. I've interacted with a lot of companies on this subject and I've found that not to be the case, though. There's usually more that an individual engineer can do about the system than sometimes they believe. It's not that there aren't management problems--there are and they are real and they do cause many or most of the failures in the software engineering industry in part. However, purely blaming management for the quality of your code is an irresponsible attitude that won't actually get you anywhere. And I don't mean "irresponsible" in the sense that you should be blamed for it, I'm taking about responsibility as the ability to be cause over your own situation, the ability to be the source of the things that you yourself produce. If you're sitting around saying that somebody else is responsible for your production all the time, then you're not going to be able to be at cause over it or come t change it in the way that you want. So yes, there are management flaws and they do cause this sort of trouble, but there's also another attitude that you can take toward it and ask yourself, "What CAN I do about my code, like for real?"
Re:Effective Engineering Productivity on Monday April 10, 2017 @05:40AM (#14077125)
Sort of, yeah. See https://testing.googleblog.com/2017/04/code-health-googles-i... as one of the examples of a type of Engineering Productivity work that I do at Google (although as you have basically pointed out, there are reasons we avoided that word for the work that I do, although I still think it falls under the broader umbrella).

It seems like the thing that you're worried about (I mean, correct me if I'm wrong, this is just the sense I get from your post) is people hiring a sketchy consultant to come in and have everybody follow some process whether or not it has anything to do with their work or making things actually better. I'm definitely also opposed to stuff like that and I've made a few jokes or snide comments about it here and there on the blog, in http://www.codesimplicity.com/book/, and on my Twitter feed.

Re:Effective Engineering Productivity on Sunday April 09, 2017 @06:56PM (#14074773)
Sort of. The Toolsmith, Tester, and Language Lawyer would all have some aspect of Engineering Productivity in their role. But it's more than just that. See also, for example: https://testing.googleblog.com/2017/04/code-health-googles-i...
Re:Effective Engineering Productivity on Sunday April 09, 2017 @06:52PM (#14074761)
On the mobile theme, I'd suggest filing your complaint with wordpress.org. This is the standard Wordpress mobile theme, so it's the mobile format used by a significant percentage of all the websites on the Internet.

On the line width, are you referring to the desktop site or the mobile one?

Re:Effective Engineering Productivity on Sunday April 09, 2017 @06:49PM (#14074750)
I think you have misunderstood what an engineering productivity worker is. It's anybody who works on tools, frameworks, systems, processes, practices, etc. that help make developers lives better.
Re:Effective Engineering Productivity on Sunday April 09, 2017 @04:36PM (#14074240)
Yes, but the post is about a group of people or an individual who works in a particular field, not the subject of productivity itself. So I defined the phrase as used in the post.

I do have another post about measuring productivity: http://www.codesimplicity.com/post/measuring-developer-produ...

Re:Effective Engineering Productivity on Sunday April 09, 2017 @03:51PM (#14074039)
In the context of this blog post, it's a group of people (or individuals) who work to improve the developer experience, usually including testing, code quality work, and practices. It sometimes also includes tooling, release work, frameworks, etc.