ABONAMENTE VIDEO REDACȚIA
RO
EN
Numărul 159
NOU
Numărul 158
Numărul 157 Numărul 156 Numărul 155 Numărul 154 Numărul 153 Numărul 152 Numărul 151 Numărul 150 Numărul 149 Numărul 148 Numărul 147 Numărul 146 Numărul 145 Numărul 144 Numărul 143 Numărul 142 Numărul 141 Numărul 140 Numărul 139 Numărul 138 Numărul 137 Numărul 136 Numărul 135 Numărul 134 Numărul 133 Numărul 132 Numărul 131 Numărul 130 Numărul 129 Numărul 128 Numărul 127 Numărul 126 Numărul 125 Numărul 124 Numărul 123 Numărul 122 Numărul 121 Numărul 120 Numărul 119 Numărul 118 Numărul 117 Numărul 116 Numărul 115 Numărul 114 Numărul 113 Numărul 112 Numărul 111 Numărul 110 Numărul 109 Numărul 108 Numărul 107 Numărul 106 Numărul 105 Numărul 104 Numărul 103 Numărul 102 Numărul 101 Numărul 100 Numărul 99 Numărul 98 Numărul 97 Numărul 96 Numărul 95 Numărul 94 Numărul 93 Numărul 92 Numărul 91 Numărul 90 Numărul 89 Numărul 88 Numărul 87 Numărul 86 Numărul 85 Numărul 84 Numărul 83 Numărul 82 Numărul 81 Numărul 80 Numărul 79 Numărul 78 Numărul 77 Numărul 76 Numărul 75 Numărul 74 Numărul 73 Numărul 72 Numărul 71 Numărul 70 Numărul 69 Numărul 68 Numărul 67 Numărul 66 Numărul 65 Numărul 64 Numărul 63 Numărul 62 Numărul 61 Numărul 60 Numărul 59 Numărul 58 Numărul 57 Numărul 56 Numărul 55 Numărul 54 Numărul 53 Numărul 52 Numărul 51 Numărul 50 Numărul 49 Numărul 48 Numărul 47 Numărul 46 Numărul 45 Numărul 44 Numărul 43 Numărul 42 Numărul 41 Numărul 40 Numărul 39 Numărul 38 Numărul 37 Numărul 36 Numărul 35 Numărul 34 Numărul 33 Numărul 32 Numărul 31 Numărul 30 Numărul 29 Numărul 28 Numărul 27 Numărul 26 Numărul 25 Numărul 24 Numărul 23 Numărul 22 Numărul 21 Numărul 20 Numărul 19 Numărul 18 Numărul 17 Numărul 16 Numărul 15 Numărul 14 Numărul 13 Numărul 12 Numărul 11 Numărul 10 Numărul 9 Numărul 8 Numărul 7 Numărul 6 Numărul 5 Numărul 4 Numărul 3 Numărul 2 Numărul 1
×
▼ LISTĂ EDIȚII ▼
Numărul 159
Abonamente

Programming in 2025: Interview with Mark Seemann

Ovidiu Mățan
Fondator @ Today Software Magazine



PROGRAMARE

How should a programmer work in the era of AI? Any tip & tricks that you apply ?

Mark Seemann: I don't want to tell anyone else how they should work, but I can share some thoughts. Two years ago, at IT Days, in my keynote I spoke about epistemology, which is the philosophy of knowledge. It applies to science in general, but also to software development. The gist of it is that empirical methods require that we make falsifiable predictions about the future.

You can do that with LLMs as well. Ask it to write a test and then run the test to verify your prediction that the test fails. Ask an LLM to write implementation code and verify your prediction that all tests now pass.

This latter part, however, may be necessary, but isn't sufficient. Consider the degenerate case: If you have no tests, and ask an LLM to write implementation code, then subsequently 'all' tests 'still' pass. This is what in logic is known as a vacuous truth.

It all boils down to the fundamental question: How do you know that the work an LLM performs on your behalf is aligned with your goals?

I think you need to find systematic, scientific ways of determining answers to that question. In the end, I find LLMs much less useful than most people seem to, but I do use them when I have easy ways to verify that their answers are aligned with my goals.

One of the new AI effects that we see now in the industry is the lack of jobs for newcomers. What do you think about this and how the teams will look in few years?

Mark Seemann: This is a really difficult question to answer. To be honest, I'm mostly inclined to believe that we're still in a big hype bubble related to LLMs, and that the bubble will burst in a couple of years. If so, we may settle on a new plateau, as per the Gartner Hype Cycle. I think we'll learn that LLMs are 'productivity tools' for programmers, but that they aren't going to replace programmers. Not even junior programmers.

But it may just be that that's what I hope, and that my prediction is influenced by that. I'm not making any bets.

We are glad that you will join us at IT Days and this year we are proud to have an exclusivity from your side. It will be the only conference in 2025 where you will be on stage. Tell us about your presentation at IT Days.

Mark Seemann: The title is 'Worse is Better', based off Richard P. Gabriel's phrase. I want to talk about how mainstream technology often isn't cutting-edge technology, and why that is. In the end, it's about trade-offs. As I often say: You can only use the right tool for the job if you know about more than one tool.

If it is possible to exclude the AI related tools, what a software engineer should learn more in 2025?

Mark Seemann: Learn fundamentals, because they tend to never grow old. I wrote an article about that last year[^1]. Learn algorithms, design patterns, SQL, HTTP, FP, OOP, etc.

Your blog is really popular. Which are the most read topics ?

Mark Seemann: A bit surprising, to me at least, is that in the last seven years, a recent article titled You'll regret using natural keys seems to be the most popular. Other than that, the most popular content is actually quite old articles about Dependency Injection.

If you will have a team tomorrow to create a new product. What that product will be ?

Mark Seemann: That would be a commercial secret.

LANSAREA NUMĂRULUI 159

Programarea, securitatea și AI-ul

Marți, 30 Septembrie, ora 18:00

msg systems Romania

Timișoara

Facebook Meetup StreamEvent YouTube

Conferință TSM

NUMĂRUL 158 - Software Optimization

Sponsori

  • BT Code Crafters
  • Bosch
  • Betfair
  • MHP
  • BoatyardX
  • .msg systems
  • P3 group
  • Ing Hubs
  • Cognizant Softvision
  • GlobalLogic
  • BMW TechWorks Romania

INTERVIU