feat: added a new post about the HP poster fair

1 files changed, 3 insertions, 3 deletions

diff --git a/content/posts/dijkstra-knuth.md b/content/posts/dijkstra-knuth.md
index ca73407..a284a1e 100644
--- a/content/posts/dijkstra-knuth.md
+++ b/content/posts/dijkstra-knuth.md
@@ -10,7 +10,7 @@ I believe it to be the most important thing I have learned about the field itsel
 Here is why.
 Dealing with complex problems is hard. 
 Programming is all about solving complex problems, programmers live by optimizing our code the best we can, and try to find solutions to problems that we encounter while doing so.
-While it is no doubt nice to have a working code that does something cool, or a solution to a problem that meets the specification, I don't think that is the mindset a programmer should have -- that is, at this stage, to solve a problem is not about getting to a solution _somehow_. 
+While it is no doubt nice to have a working code that does something cool, or a solution to a problem that meets the specification, I don't think that is the mindset a programmer should have -- that is, at this stage, to solve a problem is not about getting to a solution somehow. 
 
 Solving coding tasks requires time. 
 This might be difficult to admit for some, as it has been for me. 
@@ -19,7 +19,7 @@ Needless to say, if you have solved a problem without asking questions about it,
 Reading code is hard. 
 It's sometimes like reading an essay in a foreign language. 
 Your head hurts, your eyes are getting sore, and after 6 hours of staring at the screen you conclude you don't understand anything anymore.
-One of my favourite quotes about computing from Temple OS creator, [Terry Davis](https://en.wikipedia.org/wiki/Terry_A._Davis), reflects this perfectly (it's too long to include here, so [this is the link to the GoodReads quote page](https://www.goodreads.com/quotes/10916333-what-s-reality-i-don-t-know-when-my-bird-was-looking)).
+One of my favourite quotes about computing from Temple OS creator, [Terry Davis](https://en.wikipedia.org/wiki/Terry_A._Davis), reflects this perfectly _What’s reality? I don’t know. When my bird was looking at my computer monitor I thought, ‘That bird has no idea what he’s looking at.’ And yet what does the bird do? Does he panic? No, he can’t really panic, he just does the best he can. Is he able to live in a world where he’s so ignorant? Well, he doesn’t really have a choice. The bird is okay even though he doesn’t understand the world. You’re that bird looking at the monitor, and you’re thinking to yourself, ‘I can figure this out.’ Maybe you have some bird ideas. Maybe that’s the best you can do._
 It would almost seem like this time has been wasted, since you might have not produced a line of code.
 Nevertheless, this is all there is to programming.
 
@@ -30,6 +30,6 @@ There it is.
 Computing takes time. 
 There's no silver bullet yet, and we as programmers have to take our time to think about problems in depth. 
 There have been many comments on the peculiar style of teaching and way of being of Edsgar Dijkstra, but I believe he has made some really good points about this too. 
-What describes my experience over the last 3 years well is his quote: _The competent programmer is fully aware of the strictly limited size of his own skull; therefore he approaches the programming task in full humility[...]_. 
+What describes my experience over the last 3 years well is his quote: _The competent programmer is fully aware of the strictly limited size of his own skull; therefore he approaches the programming task in full humility[...]._ 
 I think this the approach to take, because so often computers help us verify and point out that we indeed really don't know anything, we are just pretending we do.