Threads for ChrisIsD

  1. 1

    Here’s the link to the blog post explaining the release:

    1. 6

      This is a tough problem because the intersection of git users and word users isn’t very big. In my opinion, using git with word would be helpful only if it helped in resolving merge conflicts when two documents diverge. If you have ever written something collaborative in word, you know that resolving conflicts is a big pain, especially when they involve more than just text, like tables and formatting. The build-in tool is helpful to an extent but it mostly works when you have a parent and a sibling document instead of two cousins.

      Most people I have worked with, have developed their very own version control system for word based on the hot potato model: one author at a time, manuscript gets passed along by email, append your initials at the end of the file name. It is simple and works well most of the time. More advanced workflow involve assigning people specific sections to edit that then get copy-pasted into the parent document.

      What problem would adding git to this workflow solve? I am asking because my lab doesn’t use git even for source code so asking them to use it for our documents is probably a bridge too far.

      1. 2

        I’m in this intersection and would love to grow it amongst my colleagues

        The problems I’m looking to solve though are better described as arising from the wysiwyg mixing of data input and formatting input

      1. 18

        The expectations of a professional/licensed engineer can be fulfilled whether producing code or writing emails as much as they can by building bridges. I studied electrical engineering (and computer science) but haven’t touched a circuit in 4 years. Currently I’m applying for professional recognition, and of the 16 competencies the body wants to see, there is no requirement for anything physical.

        This body’s definition of what makes an engineer includes:

        • ethical behaviour
        • how you analyse problems
        • how you keep up to date on industry practice
        • how you communicate with peers and stakeholders
        • how you manage risk

        Some lessons I feel can be learnt from software practices: Agility, being able to plan for uncertainty particularly for problems where the solution is not known immediately; Revision management, version control was one of the first things I learnt in software and I’m constantly explaining to traditional engineers why it’s important for any publication.

        Some lessons I feel software practices could learn from traditional engineering: Stakeholder management; problem analysis (surprised how few sketches and produced for software systems compared with even the management systems I work with); communication.

        I’d say anyone working with software - from coder to management - can fulfill the behaviours expected of an engineer; many engineers build their communities without ever touching CAD or concrete.

        1. 4

          Forgive my ignorance but how exactly do they define ethical behaviour?

          I’d argue that someone working on literal bombs is highly likely more of an engineer than I am, yet I find that much much much less ethical than anything I’d ever work on.

          1. 3

            They would define it in a way that doesn’t touch anywhere close to that. I think it is the same way that Christian theology was able to exclude war acts from the “do not kill” thing. Any government recognized organization would be expected to do the same leaps.

            I suspect any safety considerations attached to ethical behavior would be for things not including when the thing drops from the sky. Like not accidently blowing up when being hit lightly by a hammer…

            1. 3

              Search for “{name of institution} code of ethics” to answer this. Some examples:

              And specifically in computering:

              1. 3

                Bombs are not unethical.

                You could use bombs to excavate a mine. You could use bombs to stop a horde of murderers coming to your town.

                If it is ethical to kill in self-defense, then it is ethical to build tools that could be used to kill in self-defense.

                1. 4

                  Maintaining ignorance towards what your employer will use your work for, because hypothetically it could be used for something not-unethical, is not ethical behavior. You can assume that in OP’s question they’d be working for the military industrial complex.

                  The only thing necessary for the triumph of evil is for good men to do nothing. As an engineer, you can make a difference. You’re a scarce resource. Simply choosing to work in a place that does good takes labor away from places that do evil or do “nothing”. And your wage will always be good enough to not have to do “nothing” at a place that does evil.

                  1. 3

                    The idea that it is ethical to kill in self defence is not universal. There are some that argue it is better to die than to kill. Also, though you could use a bomb to excavate a mine, that is not it’s purpose. Bomb is defined in wiktionary as “An explosive device used or intended as a weapon”. If an explosive device is designed and used for excavation it is not a bomb.

                    Sorry to nitpick, I know these points are very niche. I simply want to point out that the statement ‘bombs are not unethical’ is open to debate.

                  2. 2

                    The other response to your comment (leeg) is spot on. For example, the organisation I’m seeking to recognise me has a code of ethics defined by: Demonstrate integrity, Practise competently, Exercise leadership, Promote sustainability. Deeper definitions are available in their code, and these definitions would allow defence workers, infrastructure builders, and software implementers to practice within their ethical framework.

                    Part of such recognition is picking a professional body which is compatible with your personal code of ethics. If you are seeking people who have such recognition, then you could use the recognising body’s code of ethics to evaluate these people.

                    Coincidentally, hours after my previous post I met an engineer who worked with bombs, though his were used to dig tunnels for highways and rail ;)

                  3. 1

                    When I took some EE a decade ago (switched to computer science, didn’t have the will to endure EE), I remember they had some specific reason why “software engineering” wasn’t an engineering discipline. I only wish I could remember what it was. I believe in Canada it wasn’t recognized at the time. The engineers saying this were certainly within the bounds of “physical engineering” - that is to say, their craft built upon real physical things instead of upon an “world”/architecture we as a species defined.

                    I much prefer the list you have. I feel that is the a great direction for the industry.

                    1. 2

                      If you’re interested in further depth on this, Engineers Australia is the organisation I’m referring to. People who undertook accredited study and work with software, whether it be computer games or medical devices, can be recognised as professional engineers based on their behaviours rather than strict preconceived notions (such as typically evidenced by exam).

                  1. 4

                    What about a bible/book cipher?

                    Cheap - cost of a bible and time to set it up

                    Charges from x - is “powered” as long as you have a light source

                    Can be stored separate from power source (e.g. A safe)

                    Lifespan extension - can be photocopied or re-written to a new medium if the old one is degrading

                    Physical useability, screen, keyboard and track pad all absent; storage, low capacity; performance, slow

                    1. 1

                      Could you elaborate on how this works? Is this where you make a secret compartment in a thicc book?

                      1. 4

               - to get an idea

                        Book cipher is about recording a code that corresponds to word or letter offsets within a particular book. The amount of offset and book can be easily accessible, but the starting position within the book is the secret.

                    1. 6

                      I feel the gains here are related to Japanese culture. Take people that work 60-80 hours per week (12-16 per day), and reduce that to say 48 and people become more productive (Ford’s research?)

                      The headline baits the idea of moving from 40 hour week to 32, but would that really see the same productivity gain?