Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Cyborg)
  • No Skin
Collapse
Brand Logo

CIRCLE WITH A DOT

  1. Home
  2. Uncategorized
  3. I am losing it at how many of my peers have forgotten what software engineering is.

I am losing it at how many of my peers have forgotten what software engineering is.

Scheduled Pinned Locked Moved Uncategorized
18 Posts 14 Posters 0 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • bert_hubert@eupolicy.socialB bert_hubert@eupolicy.social

    I am losing it at how many of my peers have forgotten what software engineering is. It is not typing in lines of code.

    abucci@buc.ciA This user is from outside of this forum
    abucci@buc.ciA This user is from outside of this forum
    abucci@buc.ci
    wrote last edited by
    #4
    @bert_hubert@eupolicy.social This really makes me wonder whether the decades of constant blog posts about method, such as software craftsmanship, *-driven design, agile, extreme programming, etc etc etc (event sourcing, the hexagonal architecture, etc etc etc etc etc dear lord there are so many), were all, ultimately, not serious. If a single technological advance coupled with hype and corporate pressure is enough to convince people to throw all of that out, how serious could it have been, really?
    rotnroll666@mastodon.socialR drscriptt@oldbytes.spaceD 2 Replies Last reply
    0
    • bert_hubert@eupolicy.socialB bert_hubert@eupolicy.social

      I am losing it at how many of my peers have forgotten what software engineering is. It is not typing in lines of code.

      notbobbytables@infosec.exchangeN This user is from outside of this forum
      notbobbytables@infosec.exchangeN This user is from outside of this forum
      notbobbytables@infosec.exchange
      wrote last edited by
      #5

      @bert_hubert Programmers convert problems into code.
      Unfortunately, programmers also convert code into problems.

      1 Reply Last reply
      0
      • bert_hubert@eupolicy.socialB bert_hubert@eupolicy.social

        I am losing it at how many of my peers have forgotten what software engineering is. It is not typing in lines of code.

        andrybak@mastodon.socialA This user is from outside of this forum
        andrybak@mastodon.socialA This user is from outside of this forum
        andrybak@mastodon.social
        wrote last edited by
        #6

        @bert_hubert that's right, it is actually mostly typing in Slack and MS Teams messages /joke

        unlofl@mstdn.socialU 1 Reply Last reply
        0
        • rotopenguin@mastodon.socialR rotopenguin@mastodon.social

          @bert_hubert it is also indenting lines of code

          freelon@mas.toF This user is from outside of this forum
          freelon@mas.toF This user is from outside of this forum
          freelon@mas.to
          wrote last edited by
          #7

          @rotopenguin with tabs or spaces though? 😜

          1 Reply Last reply
          0
          • abucci@buc.ciA abucci@buc.ci
            @bert_hubert@eupolicy.social This really makes me wonder whether the decades of constant blog posts about method, such as software craftsmanship, *-driven design, agile, extreme programming, etc etc etc (event sourcing, the hexagonal architecture, etc etc etc etc etc dear lord there are so many), were all, ultimately, not serious. If a single technological advance coupled with hype and corporate pressure is enough to convince people to throw all of that out, how serious could it have been, really?
            rotnroll666@mastodon.socialR This user is from outside of this forum
            rotnroll666@mastodon.socialR This user is from outside of this forum
            rotnroll666@mastodon.social
            wrote last edited by
            #8

            @abucci @bert_hubert lovely point. And I’m not saying you are wrong. Only few of the proponents of the things mentioned did not pivot the last two conference seasons.

            1 Reply Last reply
            0
            • rotopenguin@mastodon.socialR rotopenguin@mastodon.social

              @bert_hubert it is also indenting lines of code

              nymnympseudonymm@mstdn.scienceN This user is from outside of this forum
              nymnympseudonymm@mstdn.scienceN This user is from outside of this forum
              nymnympseudonymm@mstdn.science
              wrote last edited by
              #9

              @rotopenguin @bert_hubert Found the Python and Fortran enjoyer

              1 Reply Last reply
              0
              • blackikeeagle@mastodon.pirateparty.beB blackikeeagle@mastodon.pirateparty.be

                @bert_hubert <sarcasm>Are you not happy with progress? Just architect something and the LLM will even review itself. We no longer need those annoying "why this, why that" people anymore. Move fast and .... who knows</sarcasm>

                nymnympseudonymm@mstdn.scienceN This user is from outside of this forum
                nymnympseudonymm@mstdn.scienceN This user is from outside of this forum
                nymnympseudonymm@mstdn.science
                wrote last edited by
                #10

                @BlackIkeEagle @bert_hubert all joking aside, most large software companies now have automation pipelines that do exactly that: take a Bug off the queue, propose a fix, compile, run unit tests, run regression suites, review and comment the implementation, write up the fix make the patch ready for review.

                Sure they only cleanly fix a fraction of the bugs. But that fraction is increasing.

                stumpythemutt@social.linux.pizzaS 1 Reply Last reply
                0
                • nymnympseudonymm@mstdn.scienceN nymnympseudonymm@mstdn.science

                  @BlackIkeEagle @bert_hubert all joking aside, most large software companies now have automation pipelines that do exactly that: take a Bug off the queue, propose a fix, compile, run unit tests, run regression suites, review and comment the implementation, write up the fix make the patch ready for review.

                  Sure they only cleanly fix a fraction of the bugs. But that fraction is increasing.

                  stumpythemutt@social.linux.pizzaS This user is from outside of this forum
                  stumpythemutt@social.linux.pizzaS This user is from outside of this forum
                  stumpythemutt@social.linux.pizza
                  wrote last edited by
                  #11

                  @Nymnympseudonymm @BlackIkeEagle @bert_hubert Are the bugs that trivial? The kind I run into are "router drops packets every 55 seconds when packets per second exceeds 900"

                  nymnympseudonymm@mstdn.scienceN 2 Replies Last reply
                  0
                  • stumpythemutt@social.linux.pizzaS stumpythemutt@social.linux.pizza

                    @Nymnympseudonymm @BlackIkeEagle @bert_hubert Are the bugs that trivial? The kind I run into are "router drops packets every 55 seconds when packets per second exceeds 900"

                    nymnympseudonymm@mstdn.scienceN This user is from outside of this forum
                    nymnympseudonymm@mstdn.scienceN This user is from outside of this forum
                    nymnympseudonymm@mstdn.science
                    wrote last edited by
                    #12

                    @StumpyTheMutt @BlackIkeEagle @bert_hubert typical example: program dumps core under crazy ass stress coverage test

                    1 Reply Last reply
                    0
                    • stumpythemutt@social.linux.pizzaS stumpythemutt@social.linux.pizza

                      @Nymnympseudonymm @BlackIkeEagle @bert_hubert Are the bugs that trivial? The kind I run into are "router drops packets every 55 seconds when packets per second exceeds 900"

                      nymnympseudonymm@mstdn.scienceN This user is from outside of this forum
                      nymnympseudonymm@mstdn.scienceN This user is from outside of this forum
                      nymnympseudonymm@mstdn.science
                      wrote last edited by
                      #13

                      @StumpyTheMutt @BlackIkeEagle @bert_hubert and whether your packet drops can be repro'd, what skills you have written up, how good your design docs are

                      drscriptt@oldbytes.spaceD 1 Reply Last reply
                      0
                      • andrybak@mastodon.socialA andrybak@mastodon.social

                        @bert_hubert that's right, it is actually mostly typing in Slack and MS Teams messages /joke

                        unlofl@mstdn.socialU This user is from outside of this forum
                        unlofl@mstdn.socialU This user is from outside of this forum
                        unlofl@mstdn.social
                        wrote last edited by
                        #14

                        @andrybak @bert_hubert Lets not forget digging through jira for hours going "oh wait, heres a related... oh fuck this even worse than I thought" over and over again

                        1 Reply Last reply
                        0
                        • bert_hubert@eupolicy.socialB bert_hubert@eupolicy.social

                          I am losing it at how many of my peers have forgotten what software engineering is. It is not typing in lines of code.

                          woody@pleroma.pch.netW This user is from outside of this forum
                          woody@pleroma.pch.netW This user is from outside of this forum
                          woody@pleroma.pch.net
                          wrote last edited by
                          #15
                          @bert_hubert

                          Of course not, that's for the olds. It has something to do with vibing.
                          1 Reply Last reply
                          0
                          • bert_hubert@eupolicy.socialB bert_hubert@eupolicy.social

                            I am losing it at how many of my peers have forgotten what software engineering is. It is not typing in lines of code.

                            josh@hactivedirectory.comJ This user is from outside of this forum
                            josh@hactivedirectory.comJ This user is from outside of this forum
                            josh@hactivedirectory.com
                            wrote last edited by
                            #16

                            @bert_hubert Pfft no. It's Jira. <runs>

                            1 Reply Last reply
                            0
                            • nymnympseudonymm@mstdn.scienceN nymnympseudonymm@mstdn.science

                              @StumpyTheMutt @BlackIkeEagle @bert_hubert and whether your packet drops can be repro'd, what skills you have written up, how good your design docs are

                              drscriptt@oldbytes.spaceD This user is from outside of this forum
                              drscriptt@oldbytes.spaceD This user is from outside of this forum
                              drscriptt@oldbytes.space
                              wrote last edited by
                              #17

                              @Nymnympseudonymm @StumpyTheMutt @BlackIkeEagle @bert_hubert I dare say that a lot of the investigation has been done to identify the behavioral problem by the time you get to this point. I think this work effort is where much over hyped automation fails.

                              1 Reply Last reply
                              0
                              • abucci@buc.ciA abucci@buc.ci
                                @bert_hubert@eupolicy.social This really makes me wonder whether the decades of constant blog posts about method, such as software craftsmanship, *-driven design, agile, extreme programming, etc etc etc (event sourcing, the hexagonal architecture, etc etc etc etc etc dear lord there are so many), were all, ultimately, not serious. If a single technological advance coupled with hype and corporate pressure is enough to convince people to throw all of that out, how serious could it have been, really?
                                drscriptt@oldbytes.spaceD This user is from outside of this forum
                                drscriptt@oldbytes.spaceD This user is from outside of this forum
                                drscriptt@oldbytes.space
                                wrote last edited by
                                #18

                                @abucci @bert_hubert the people that researched and authored said blogs were very serious. Sadly many of those paying said authors to do the work that prompted the articles weren’t equally serious.

                                1 Reply Last reply
                                0
                                • R relay@relay.an.exchange shared this topic
                                Reply
                                • Reply as topic
                                Log in to reply
                                • Oldest to Newest
                                • Newest to Oldest
                                • Most Votes


                                • Login

                                • Login or register to search.
                                • First post
                                  Last post
                                0
                                • Categories
                                • Recent
                                • Tags
                                • Popular
                                • World
                                • Users
                                • Groups