GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Conversation

Notices

  1. Embed this notice
    Kristen Foster-Marks (kfostermarks@mastodon.social)'s status on Sunday, 25-Feb-2024 03:40:34 JST Kristen Foster-Marks Kristen Foster-Marks

    Lit reviewing "developer experience" as a construct and earliest thing I found in initial search is from Fagerholm and Münch(2012):

    F. Fagerholm and J. Münch, "Developer experience: Concept and definition," 2012 International Conference on Software and System Process (ICSSP), Zurich, Switzerland, 2012, pp. 73-77, doi: 10.1109/ICSSP.2012.6225984.

    It doesn't reference any existing literature on developer experience. Google ngram also shows a HUGE spike in "developer experience" mentions in 2013.

    In conversation Sunday, 25-Feb-2024 03:40:34 JST from mastodon.social permalink
    • Embed this notice
      Paul Cantrell (inthehands@hachyderm.io)'s status on Sunday, 25-Feb-2024 03:40:32 JST Paul Cantrell Paul Cantrell
      in reply to

      @KFosterMarks
      Hmmm, I can’t remember when that specific term entered my world. Certainly for example that idea by whatever name shows up very clearly in the design and marketing of Ruby on Rails, the IDEs of the mid 90s (CodeWarrior, Think C), Turbo Pascal, Beagle Brothers, Smalltalk…

      In conversation Sunday, 25-Feb-2024 03:40:32 JST permalink
    • Embed this notice
      Kristen Foster-Marks (kfostermarks@mastodon.social)'s status on Sunday, 25-Feb-2024 03:40:34 JST Kristen Foster-Marks Kristen Foster-Marks
      in reply to

      For those who have been in the software development & engineering space for awhile: Does this feel temporally accurate? Do you remember talking about "developer experience" way ahead of 2012? I'm wondering if industry informed research focus with this paper, or if the paper and operationalization of the term informed industry.

      In conversation Sunday, 25-Feb-2024 03:40:34 JST permalink
    • Embed this notice
      Cat Hicks (grimalkina@mastodon.social)'s status on Sunday, 25-Feb-2024 03:40:47 JST Cat Hicks Cat Hicks
      in reply to
      • Greg Wilson
      • Jeremy Kahn

      @trochee @gvwilson @KFosterMarks Also, Zinsser's chapter on business writing is a fave of mine:

      "If you have to do any writing in your job, this chapter is for you. Just as in science writing, anxiety is a big part of the problem and humanity and clear thinking are a big part of the solution."

      In conversation Sunday, 25-Feb-2024 03:40:47 JST permalink
      Paul Cantrell repeated this.
    • Embed this notice
      Cat Hicks (grimalkina@mastodon.social)'s status on Sunday, 25-Feb-2024 03:40:48 JST Cat Hicks Cat Hicks
      in reply to
      • Greg Wilson
      • Jeremy Kahn

      @trochee @gvwilson @KFosterMarks Bob Sutton credits the term to Polly LaBarre ! I don't have an OG source but love it.

      In conversation Sunday, 25-Feb-2024 03:40:48 JST permalink
      Paul Cantrell repeated this.
    • Embed this notice
      Greg Wilson (gvwilson@mastodon.social)'s status on Sunday, 25-Feb-2024 03:40:49 JST Greg Wilson Greg Wilson
      in reply to

      @KFosterMarks I remember a Sun Microsystems rep talking about "programmer comfort" in the late 1980s (more specifically, as something they had that IBM and SGI didn't). I also remember the phrase "engineering ergonomics" from about the same time, but can't recall context. The idea was definitely used by Unix fans as a stick to beat up Windows in that period even if the name varied.

      In conversation Sunday, 25-Feb-2024 03:40:49 JST permalink
    • Embed this notice
      Cat Hicks (grimalkina@mastodon.social)'s status on Sunday, 25-Feb-2024 03:40:49 JST Cat Hicks Cat Hicks
      in reply to
      • Greg Wilson

      @gvwilson @KFosterMarks the use of "ergonomics" to cover everything from chairs to core psychological needs haunts me as a piece of business jargon monoxide 😭

      In conversation Sunday, 25-Feb-2024 03:40:49 JST permalink
    • Embed this notice
      Jeremy Kahn (trochee@dair-community.social)'s status on Sunday, 25-Feb-2024 03:40:49 JST Jeremy Kahn Jeremy Kahn
      in reply to
      • Greg Wilson
      • Cat Hicks

      @grimalkina

      💚 Will be using "jargon monoxide poisoning" I just haven't found the right place yet

      @gvwilson @KFosterMarks

      In conversation Sunday, 25-Feb-2024 03:40:49 JST permalink
    • Embed this notice
      Cat Hicks (grimalkina@mastodon.social)'s status on Sunday, 25-Feb-2024 03:40:53 JST Cat Hicks Cat Hicks
      in reply to
      • Greg Wilson
      • Jeremy Kahn

      @trochee @gvwilson @KFosterMarks Also poignant in a way that I did not realize back when I first read this book, not yet doing research on the isolation of engineering teams, he wrote: "Go to the engineer who conceived the new system," I said, "or to the designer who designed it, or to the technician who assembled it, and get them to tell you in their own words how the idea came to them, or how they put it together, or how it will be used by real people in the real world."

      ❤️

      In conversation Sunday, 25-Feb-2024 03:40:53 JST permalink
    • Embed this notice
      Paul Cantrell (inthehands@hachyderm.io)'s status on Sunday, 25-Feb-2024 04:20:30 JST Paul Cantrell Paul Cantrell
      in reply to

      @KFosterMarks
      Hmm, after mulling a bit: I wonder if you’d find origins of this in the way Grace Hopper talked about FLOW-MATIC?

      In conversation Sunday, 25-Feb-2024 04:20:30 JST permalink
    • Embed this notice
      Paul Cantrell (inthehands@hachyderm.io)'s status on Monday, 26-Feb-2024 01:34:00 JST Paul Cantrell Paul Cantrell
      in reply to

      @KFosterMarks Ha, I was hoping you’d do my research for me! 😜 I'm not sure how she talked about it either, and am curious.

      I mention it because FLOW-MATIC was more or less the first programming language designed for readability. Predecessors were concerned with efficient coding, efficient execution, and ease of implementation. FLOW-MATIC used English-like syntax with full words — very costly on machines of the time! Clearly she was looking in the direction you're investigating.

      In conversation Monday, 26-Feb-2024 01:34:00 JST permalink
    • Embed this notice
      Kristen Foster-Marks (kfostermarks@mastodon.social)'s status on Monday, 26-Feb-2024 01:34:01 JST Kristen Foster-Marks Kristen Foster-Marks
      in reply to
      • Paul Cantrell

      @inthehands

      Ooooh Paul can you tell me more? Tbh, I'm swimming in investigatory paths to follow up on in through the many responses to my original question, and won't have time to deep dive on each one - how did Grace Hopper talk about FLOW-MATIC?

      In conversation Monday, 26-Feb-2024 01:34:01 JST permalink
    • Embed this notice
      Paul Cantrell (inthehands@hachyderm.io)'s status on Monday, 26-Feb-2024 01:35:08 JST Paul Cantrell Paul Cantrell
      in reply to

      @KFosterMarks FLOW-MATIC lead to COBOL, which was much more of a design-by-committee monstrosity (and of course hugely important, still used today). But my impression is that FLOW-MATIC is much more Grace Hopper’s mid-50s vision. She was looking far ahead, and saw something others didn’t.

      In conversation Monday, 26-Feb-2024 01:35:08 JST permalink

Feeds

  • Activity Streams
  • RSS 2.0
  • Atom
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.