8.14.0.4

Postlude🔗

🔗

    Onward

    AI

    A Mindset for Life

 

 

hiring

AI

life

Onward🔗

How to identify socially responsible software developers among college applicants.

– If you’re a manager who thinks of developers as interchangeable assembly line workers, you’re probably not interested in such developers. Instead you’re looking for graduates of school that teach as many courses as possible one of the currently fashionable programming languages, ideally, a somewhat older one such as Java (at the moment). They have a good amount of experience with old-fashioned code and recognize its idioms. They will learn to struggle with code constructed from such idioms, given enoug—meanigng a lot of—time.

– If you are a manager, beware of the hero programmer who can and has done “everything.” There is a place and time for such developers. In such situations, they build what you need now at a speed and at a quality level that amazes everyone. But, they rarely develop code with “lesser” maintainers in mind. When the code needs maintenance, the hero is likely no longer around. Maintenance is boring, they think and sometimes they say so. And then the team is stuck.

Seriously, let’s assume the goal is to recruit programmers who are willing to develop with an eye toward the future and/or are willing to learn.

AI🔗

Literature/What Will AI Do to Your Job? Take a Look at What It’s Already Doing to Coders - WSJ.pdf https://www.wsj.com/articles/ai-jobs-replace-tech-workers-8f3dc92?st=byph69h7vgqbv6i&reflink=desktopwebshare_permalink

A Mindset for Life🔗

Developing in a socially responsible manner means to stop at certain stages, to drop everything, to reflect on what has been produced, and to ensure that others can easily understand whatever has been written down. Such a

stop, drop, and reflect

approach will help the current team, future team members, and even outside developers, because in this day and age, the systems we built are typically open, like the running example of the preceding few sections

This chapter of the book focuses on products other than code, especially a statement of purpose, a dependency description, and interface specifications. Sometimes these products come about before developers start coding. At other times, they emerge after some code has already been written. It is probably best if these products are sketched as coding starts and are revised as coding proceeds.

stop, drop, and reflect

what have I done? how do I work? how does my work affect others?