Keep It Simple
- While studying architecture not only had I so little money that I ate spaghetti and pesto every day, I learned a thing or two about design principles as well. These principles hold true for every product or piece of engineering you plan out. It is the KISS principle. Keep it simple stupid, or to quote a guy Jony Ive is clearly a fan of [1]: -“Good design is as little design as possible.”- -
— Dieter Rams —
- Let’s expand on it so far that it should be as simple as possible without being outright stupid. To expand even further, a compelling and useful design is not only measurable by the things you can do with it, but even more important are the things you don’t have to do when you use it. -
--As you craft something, you will inevitably communicate with everybody using your product. In proxy, any room, place or inanimate object created by a human speaks to the user. Even on an emotional level. Psychologists or product designers like computer and car designers are no strangers to this. Donald Norman wrote multiple books about it [2], [3]. Some good reads. Schulz von Thun defined the four-ears model in which a sender’s message is received on four different levels. These are Factual information, Appeal, Self-revelation and Relationship. This means it is helpful to think about the essence of the aspect you want to craft to communicate clearly and get the message across. +
2021-06-01
+Keep It Simple
+While studying architecture not only had I so little money that I ate +spaghetti and pesto every day, I learned a thing or two about design +principles as well. These principles hold true for every product or +piece of engineering you plan out. It is the KISS principle. Keep it +simple stupid, or to quote a guy Jony Ive is clearly a fan of +[1]:
+++"Good design is as little design as possible."
+
+--- Dieter Rams ---
Let's expand on it so far that it should be as simple as possible +without being outright stupid. To expand even further, a compelling and +useful design is not only measurable by the things you can do with it, +but even more important are the things you don't have to do when you use +it.
+As you craft something, you will inevitably communicate with everybody
+using your product. In proxy, any room, place or inanimate object
+created by a human speaks to the user. Even on an emotional level.
+Psychologists or product designers like computer and car designers are
+no strangers to this. Donald Norman wrote multiple books about it
+[2], [3].
+Schulz von Thun defined the four-ears
+model in which a
+sender's message is received on four different levels. These are Factual
+information, Appeal, Self-revelation and Relationship. This means it is
+helpful to think about the essence of the aspect you want to craft to
+communicate clearly and get the message across. 
Pesto Principles
++
What about this website's design principles? First and foremost, how +you spent your time is important. Do you really need to wait for more +than a few seconds to load a website? Then there should be a plausible +reason for that. Should you wait more than 5 seconds to be able to read +something a guy is rambling about on his blog? I highly doubt it. The +layout should respect you and your time. Network traffic should be +minimal.
+Second, I don't want your data. No cookies, no statistics about you, no +ad tracking of your surfing behavior. That is what you and I won't have +to put up with. You may read my blog, or you don't. Take it or leave it. +But I hope you will learn something by doing it or have a good time at +least.
+There are some points to make this website work and make it accessible.
+To write entries, I will use plain HTML. For now, it is sufficient. HTML
+is a nice markup language. Use a <lang> tag and you got translation
+accessibility. Another one is the following line, making the layout
+respond dynamically to different screen sizes. More examples on this
+beautiful website.
<meta name="viewport" content="width=device-width, initial-scale=1">
+
-
--
Pesto Principles
--What about this website's design principles? First and foremost, how you spent your time is important. Do you really need to wait for more than a few seconds to load a website? Then there should be a plausible reason for that. Should you wait more than 5 seconds to be able to read something a guy is rambling about on his blog? I highly doubt it. The layout should respect you and your time. Network traffic should be minimal. - -Second, I don’t want your data. No cookies, no statistics about you, no ad tracking of your surfing behavior. That is what you and I won’t have to put up with. You may read my blog, or you don’t. Take it or leave it. But I hope you will learn something by doing it or have a good time at least. -
- There are some points to make this website work and make it accessible. To write entries, I will use plain HTML. For now, it is sufficient. HTML is a nice markup language. Use a <lang> tag and you got translation accessibility. Another one is the following line, making the layout respond dynamically to different screen sizes. More examples on this beautiful website.
-
-
-<meta name="viewport" content="width=device-width, initial-scale=1">
-
-
- This will be a blog about computers, for the most part, there will be code examples. Further, I want to keep the stylesheet small and maintainable. Monospaced fonts are not only a dead giveaway about this fact, a solid layout is created via the following line of CSS.
-
-
-.content{text-align:justify;}
-
-
-
-- To keep things in perspective, the date of publication will be the first line in each article. If the content may be of interest to you, knowing the date it was created is beneficial in evaluating its potential usefulness over time. -
--There is no harm in growing something like a website incrementally. You will never miss a feature you never had in the first place. You could aspire to get it if it is conceptually meaningful and makes some sense in the overall picture. But a feature that does not exist needs no maintenance, does not produce any bugs and needs no documentation. -
“The things you own end up owning you.”-
— Chuck Palahniuk —
Cordial Code
--The website was created on a Saturday afternoon in Python and Flask framework. Six months down the line, I do not want to put much energy into grasping what I had done this weekend regarding to code structure. I want to put the least amount of time possible into extending and maintaining the framework of the site. It consists of a Python file, a stylesheet, a jinja template and an empty favicon file. The last one exists because I want to avoid any error possible displayed in the network console of the browser. Everything else is content. +
This will be a blog about computers, for the most part, there will be +code examples. Further, I want to keep the stylesheet small and +maintainable. Monospaced fonts are not only a dead giveaway about this +fact, a solid layout is created via the following line of CSS.
+.content{text-align:justify;}
+
-A directory named blog contains all entries released as well as the ones I am working on. Metadata about subdirectories and the corresponding content is gathered inside a <key>:<value> structure. An entry is seen as valid and stored in the dictionary as soon as an index.html file is found. Who knows what might be added in the future. It will be added to a list of values. For now, metadata is solely the date of the blog articles. It is added to the RSS site automatically as well. The code snippet contains the dictionary.
-
To keep things in perspective, the date of publication will be the first +line in each article. If the content may be of interest to you, knowing +the date it was created is beneficial in evaluating its potential +usefulness over time.
+There is no harm in growing something like a website incrementally. You +will never miss a feature you never had in the first place. You could +aspire to get it if it is conceptually meaningful and makes some sense +in the overall picture. But a feature that does not exist needs no +maintenance, does not produce any bugs and needs no documentation.
+++"The things you own end up owning you."
+
+--- Chuck Palahniuk ---
Cordial Code
++
The website was created on a Saturday afternoon in Python and Flask +framework. Six months down the line, I do not want to put much energy +into grasping what I had done this weekend regarding to code structure. +I want to put the least amount of time possible into extending and +maintaining the framework of the site. It consists of a Python file, a +stylesheet, a jinja template and an empty favicon file. The last one +exists because I want to avoid any error possible displayed in the +network console of the browser. Everything else is content. You can find +the site as a repository on my git.
+A directory named blog contains all entries released as well as the
+ones I am working on. Metadata about subdirectories and the
+corresponding content is gathered inside a \<key>:\<value> structure.
+An entry is seen as valid and stored in the dictionary as soon as an
+index.html file is found. Who knows what might be added in the future.
+It will be added to a list of values. For now, metadata is solely the
+date of the blog articles. It is added to the RSS site automatically as
+well. The code snippet contains the dictionary.
meta_data = {root[len("./templates/blog/"):] :
+ datetime.fromtimestamp(os.path.getmtime(os.path.join(root,"index.html")))
+ for root, dirs, files in os.walk("./templates/blog") if "index.html" in files}
+
-
-meta_data = {root[len("./templates/blog/"):] :
- datetime.fromtimestamp(os.path.getmtime(os.path.join(root,"index.html")))
- for root, dirs, files in os.walk("./templates/blog") if "index.html" in files}
-
-
-Routes are set by the use of decorators. The landing page is declared in the following snippet. After the dictionary is sorted by date, render_template() returns a string. The result will be interpreted by the browser in HTML/CSS format.
-
-
-@app.route('/')
-def index(_paths=meta_data):
- sorted_meta_data = dict(sorted(meta_data.items(), reverse=True, key=lambda item : item[1]))
- return render_template("index.html", _paths=sorted_meta_data)
-
-
-The main page, like every other page, extends the general jinja template. It contains a list of all articles found.
-
-
-{% extends "template.html" %}
-{% block head %}
- {{ super() }}
-{% endblock %}
-{% block content %}
- <p>Welcome to my website</p>
- <span class="index">
- {% for name,_date in _paths.items() %}
- <p><a href="{{ url_for('blog', blog_item=name) }}">{{ _date.date() }} {{ name }}</a></p>
- {% endfor %}
- </span>
-{% endblock %}
-
-
-URLs originate from the meta_data dictionary keys. These are the blog entries’ directory names. Flask’s url_for() returns the articles if you want to visit the site. It handles URL encoding as well. This is pretty neat since there are spaces in the names.
-
-
-@app.route('/blog/<blog_item>/index.html')
-def blog(blog_item, _date=meta_data):
- return render_template(f"blog/{blog_item}/index.html", _date=meta_data[blog_item])
-
-
-Digestif
--Incidentally, this turned out to be not only an opener for my blog but code documentation for myself as well. Maybe, I’ll need to pick it up in six months, who knows…. -As a closure, at least from my experience, the most feature-rich application seldom reaches its set goals. The one with a clear and precise target, fulfilling its minimal scope, most likely will. -
-This is how you make pesto, by the way. Bon Appetit! -
--
References
-[1] Less and More: The Design Ethos of Dieter Rams, 2015, ISBN:9783899555844-[2] Emotional Design: Why We Love (or Hate) Everyday Things, 2005, ISBN:9780465051366 -[3] The Design of Everyday Things, 2002, ISBN, 9780465067107 - +
Routes are set by the use of decorators. The landing page is declared in
+the following snippet. After the dictionary is sorted by date,
+render_template()
+returns a string. The result will be interpreted by the browser in
+HTML/CSS format.
@app.route('/')
+ def index(_paths=meta_data):
+ sorted_meta_data = dict(sorted(meta_data.items(), reverse=True, key=lambda item : item[1]))
+ return render_template("index.html", _paths=sorted_meta_data)
+The main page, like every other page, extends the general jinja +template. It contains a list of all articles found.
+ {% extends "template.html" %}
+ {% block head %}
+ {{ super() }}
+ {% endblock %}
+ {% block content %}
+ <p>Welcome to my website</p>
+ <span class="index">
+ {% for name,_date in _paths.items() %}
+ <p><a href="{{ url_for('blog', blog_item=name) }}">{{ _date.date() }} {{ name }}</a></p>
+ {% endfor %}
+ </span>
+ {% endblock %}
+URLs originate from the meta_data dictionary keys. These are the blog
+entries' directory names. Flask's
+url_for()
+returns the articles if you want to visit the site. It handles URL
+encoding as well. This is pretty neat since there are spaces in the
+names.
@app.route('/blog/<blog_item>/index.html')
+ def blog(blog_item, _date=meta_data):
+ return render_template(f"blog/{blog_item}/index.html", _date=meta_data[blog_item])
+Digestif
++
Incidentally, this turned out to be not only an opener for my blog but +code documentation for myself as well. Maybe, I'll need to pick it up in +six months, who knows.... As a closure, at least from my experience, the +most feature-rich application seldom reaches its set goals. The one with +a clear and precise target, fulfilling its minimal scope, most likely +will.
+This is how you make pesto, by the +way. Bon Appetit!
+References
+[1] Less and More: The Design Ethos of Dieter Rams, 2015,
+ISBN:9783899555844
+[2] Emotional Design: Why We Love (or Hate) Everyday Things, 2005,
+ISBN:9780465051366
+[3] The Design of Everyday Things, 2002, ISBN,
+9780465067107
The Joy of One-Liners
-There is an engineering idiom which withstands time like no other. As old as the hills but never forgotten. In informational technology relations, one could say it is ancient. Its dawn proclaimed from the shores of Seattle, defeated by an apocalyptic horseman with the melodious name NT. Shot! Point blank into the chest. Buried under the hills of an IT dark age which we call the nineties, dead. But is it? Well, not exactly. There is still life in the old dog. Like Beatrix Kiddo, it one-inch punches itself back to daylight. Coal black as a miner. Topsoil sticks to its beige 1978’s leather jacket, it trickles to the ground with every step taken to the nearest diner. The door opens again. “May I have a glass of water, please?” - --An art passed down from the ancestors. Its most visible interface: The Shell. Its name: The Unix Philosophy. -
-Coined by Doug McIlroy in the Bell System Technical Journal as a foreword to the UNIX Time-Sharing System. There is an even more concise version[1] and according to Eric Steven Raymond this is [2]: -
“This is the Unix philosophy: Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface.”- -
— Doug McIlroy —
-In some way, this is similar to the concept of the on vogue philosophy of microservices everywhere. Services are written to do one thing and do it well. They work together. Also, text is the connecting link between programs, services, and humans. The possibility to read a program’s output as text seems benign, as long as everything is working well. The advantage is interactivity at any time, testability of every component, and debuggability at every step of the process in an on the fly manner. Impromptu, out of reflex like a punch. -
-Pipe Dreams
--Mc Ilroy made another very important contribution, which is the Unix pipe. It is the practical implementation of connecting the programs inside the shell. He saw the programs as tools, plugged together via pipes building a toolbox. Program A’s
stdout is put into the stdin of program B. This leaves us with a single line of chained, well-defined programs to solve a problem that would otherwise be an extensive, multi-line program in any programming language of your choice.
-
-Let’s say we’ve got two programs. The first is one is fortune, the fortune cookie program from BSD games, which outputs random quotes as text. The second one is cowsay, which displays various kinds of animals as ASCII art. In order to work in a coherent manner a | is used. The pipe connects the first one to the second one.
--
-
-❯ fortune | cowsay
- _________________________________________
-/ Gil-galad was an Elven-king. Of him the \
-| harpers sadly sing: the last whose |
-| realm was fair and free between the |
-| Mountains and the Sea. |
-| |
-| His sword was long, his lance was keen, |
-| his shining helm afar was seen; the |
-| countless stars of heaven's field were |
-| mirrored in his silver shield. |
-| |
-| But long ago he rode away, and where he |
-| dwelleth none can say; for into |
-| darkness fell his star in Mordor where |
-| the shadows are. |
-| |
-\ -- J. R. R. Tolkien /
- -----------------------------------------
- \ ^__^
- \ (oo)\_______
- (__)\ )\/\
- ||----w |
- || ||
-
-
--To mix in some colors pipe everything through lolcat. Try it out! -
-
-
-❯ fortune | cowsay | lolcat
-
-
--So far so good, let us gain some real-world practice. -
-Punching Lines — Retire Your Password Generator
--Have you ever questioned the integrity of your one-click, GUI, proprietary password generator? Is its randomness really as unpredictable as it proclaims? Are you the only one which ends up knowing your generated password? There is a one-liner that ups your opsec instantly. Right from the source of randomness: -
-
-❯ head -n 42 /dev/urandom | tr -cd '[:alnum:]' | cut -c-12
-
-
-So, what is going on here? Everything is a file, that is the way *nix systems see it, even the device which puts out random data. To read the upper part of a file we use head. It will be sent to stdout and displayed via the shell. Parameter -n reads exactly 42 lines of the file given to gather enough randomness. The output of head will be sent to tr. In order to select only alphanumeric characters for our password, we use '[:alnum:]'. Parameters -c selects the complement of alphanumeric characters and -d deletes them. cut does exactly what it says, -c-12 cuts after 12 characters with leaves us with a random password of length 12. Every time you execute this one-liner a freshly made random password is returned.
-
-To extend the pool of possible symbols the manual of tr lists various sets of filtered symbols. In the case of a password generator, further sensible filters are '[:alpha:]' or '[:digit:]'. While '[:graph:]' is also viable in this case it returns one of the greater sets of symbols. Use it with caution, especially if you create passwords for database users. These might be terminated prematurely through ` or ' inside the returned string.
-
Sunday Punch
--This blog entrance can be seen as a prelude to a series of one-liners I use time and time again. The are multiple in the pipeline. One-liners should save you the time you otherwise would spend coding a complex solution. There is little better than solving a challenging problem in a single line. -
-
References
-[1] A Quarter Century of Unix, 1994, Peter Salus, ISBN:9780201547771-[2] The Art of UNIX Programming, 2003, Eric Raymond, ISBN:9780131429017
- +
2022-05-29
+The Joy of One-Liners
+There is an engineering idiom which withstands time like no other. As +old as the hills but never forgotten. In informational technology +relations, one could say it is ancient. Its dawn proclaimed from the +shores of Seattle, defeated by an apocalyptic horseman with the +melodious name NT. Shot! Point blank into the chest. Buried under the +hills of an IT dark age which we call the nineties, dead. But is it? +Well, not exactly. There is still life in the old dog. Like Beatrix +Kiddo, it one-inch punches itself back to daylight. Coal black as a +miner. Topsoil sticks to its beige 1978's leather jacket, it trickles to +the ground with every step taken to the nearest diner. The door opens +again. "May I have a glass of water, please?"
+An art passed down from the ancestors. Its most visible interface: The +Shell. Its name: The Unix Philosophy.
+Coined by Doug McIlroy in the Bell System Technical +Journal as a +foreword to the UNIX Time-Sharing System. There is an even more concise +version[1] and +according to Eric Steven +Raymond this +is [2]:
+++"This is the Unix philosophy: Write programs that do one thing and do +it well. Write programs to work together. Write programs to handle +text streams, because that is a universal interface."
+
+--- Doug McIlroy ---
In some way, this is similar to the concept of the on vogue philosophy +of microservices everywhere. Services are written to do one thing and do +it well. They work together. Also, text is the connecting link between +programs, services, and humans. The possibility to read a program's +output as text seems benign, as long as everything is working well. The +advantage is interactivity at any time, testability of every component, +and debuggability at every step of the process in an on the fly manner. +Impromptu, out of reflex like a punch.
+Pipe Dreams
++
Mc Ilroy made another very important contribution, which is the Unix
+pipe. It is the practical implementation of connecting the programs
+inside the shell. He saw the programs as tools, plugged together via
+pipes building a
+toolbox. Program
+A's stdout is put into the stdin of program B. This leaves us with a
+single line of chained, well-defined programs to solve a problem that
+would otherwise be an extensive, multi-line program in any programming
+language of your choice.
Let's say we've got two programs. The first is one is fortune, the
+fortune cookie program from BSD games, which outputs random quotes as
+text. The second one is cowsay, which displays various kinds of
+animals as ASCII art. In order to work in a coherent manner a | is
+used. The pipe connects the first one to the second one.
fortune | cowsay
+ _________________________________________
+ / Gil-galad was an Elven-king. Of him the \
+ | harpers sadly sing: the last whose |
+ | realm was fair and free between the |
+ | Mountains and the Sea. |
+ | |
+ | His sword was long, his lance was keen, |
+ | his shining helm afar was seen; the |
+ | countless stars of heaven's field were |
+ | mirrored in his silver shield. |
+ | |
+ | But long ago he rode away, and where he |
+ | dwelleth none can say; for into |
+ | darkness fell his star in Mordor where |
+ | the shadows are. |
+ | |
+ \ -- J. R. R. Tolkien /
+ -----------------------------------------
+ \ ^__^
+ \ (oo)\_______
+ (__)\ )\/\
+ ||----w |
+ || ||
+To mix in some colors pipe everything through lolcat. Try it out!
+fortune | cowsay | lolcat
+So far so good, let us gain some real-world practice.
+Punching Lines and Retire Your Password Generator
++
Have you ever questioned the integrity of your one-click, GUI, +proprietary password generator? Is its randomness really as +unpredictable as it proclaims? Are you the only one which ends up +knowing your generated password? There is a one-liner that ups your +opsec instantly. Right from the source of randomness:
+head -n 42 /dev/urandom | tr -cd '[:alnum:]' | cut -c-12
+So, what is going on here? Everything is a file, that is the way *nix
+systems see it, even the device which puts out random data. To read the
+upper part of a file we use head. It will be sent to stdout and
+displayed via the shell. Parameter -n reads exactly 42 lines of the
+file given to gather enough randomness. The output of head will be
+sent to tr. In order to select only alphanumeric characters for our
+password, we use '[:alnum:]'. Parameters -c selects the complement
+of alphanumeric characters and -d deletes them. cut does exactly
+what it says, -c-12 cuts after 12 characters with leaves us with a
+random password of length 12. Every time you execute this one-liner a
+freshly made random password is returned.
To extend the pool of possible symbols the manual of tr lists various
+sets of filtered symbols. In the case of a password generator, further
+sensible filters are '[:alpha:]' or '[:digit:]'. While '[:graph:]'
+is also viable in this case it returns one of the greater sets of
+symbols. Use it with caution, especially if you create passwords for
+database users. These might be terminated prematurely through ` or
+' inside the returned string.
Sunday Punch
++
This blog entrance can be seen as a prelude to a series of one-liners I +use time and time again. The are multiple in the pipeline. One-liners +should save you the time you otherwise would spend coding a complex +solution. There is little better than solving a challenging problem in a +single line.
+References
+[1] A Quarter Century of Unix, 1994, Peter Salus,
+ISBN:9780201547771
+[2] The Art of UNIX Programming, 2003, Eric Raymond,
+ISBN:9780131429017
Keep It Simple
- While studying architecture not only had I so little money that I ate spaghetti and pesto every day, I learned a thing or two about design principles as well. These principles hold true for every product or piece of engineering you plan out. It is the KISS principle. Keep it simple stupid, or to quote a guy Jony Ive is clearly a fan of [1]: -“Good design is as little design as possible.”- -
— Dieter Rams —
- Let’s expand on it so far that it should be as simple as possible without being outright stupid. To expand even further, a compelling and useful design is not only measurable by the things you can do with it, but even more important are the things you don’t have to do when you use it. -
-
-As you craft something, you will inevitably communicate with everybody using your product. In proxy, any room, place or inanimate object created by a human speaks to the user. Even on an emotional level. Psychologists or product designers like computer and car designers are no strangers to this. Donald Norman wrote multiple books about it [2], [3]. Some good reads. Schulz von Thun defined the four-ears model in which a sender’s message is received on four different levels. These are Factual information, Appeal, Self-revelation and Relationship. This means it is helpful to think about the essence of the aspect you want to craft to communicate clearly and get the message across.
-
-  }})
-
-
Pesto Principles
--What about this website's design principles? First and foremost, how you spent your time is important. Do you really need to wait for more than a few seconds to load a website? Then there should be a plausible reason for that. Should you wait more than 5 seconds to be able to read something a guy is rambling about on his blog? I highly doubt it. The layout should respect you and your time. Network traffic should be minimal. - -Second, I don’t want your data. No cookies, no statistics about you, no ad tracking of your surfing behavior. That is what you and I won’t have to put up with. You may read my blog, or you don’t. Take it or leave it. But I hope you will learn something by doing it or have a good time at least. -
- There are some points to make this website work and make it accessible. To write entries, I will use plain HTML. For now, it is sufficient. HTML is a nice markup language. Use a <lang> tag and you got translation accessibility. Another one is the following line, making the layout respond dynamically to different screen sizes. More examples on this beautiful website.
-
-
-<meta name="viewport" content="width=device-width, initial-scale=1">
-
-
- This will be a blog about computers, for the most part, there will be code examples. Further, I want to keep the stylesheet small and maintainable. Monospaced fonts are not only a dead giveaway about this fact, a solid layout is created via the following line of CSS.
-
-
-.content{text-align:justify;}
-
-
-
-- To keep things in perspective, the date of publication will be the first line in each article. If the content may be of interest to you, knowing the date it was created is beneficial in evaluating its potential usefulness over time. -
--There is no harm in growing something like a website incrementally. You will never miss a feature you never had in the first place. You could aspire to get it if it is conceptually meaningful and makes some sense in the overall picture. But a feature that does not exist needs no maintenance, does not produce any bugs and needs no documentation. -
“The things you own end up owning you.”-
— Chuck Palahniuk —
Cordial Code
--The website was created on a Saturday afternoon in Python and Flask framework. Six months down the line, I do not want to put much energy into grasping what I had done this weekend regarding to code structure. I want to put the least amount of time possible into extending and maintaining the framework of the site. It consists of a Python file, a stylesheet, a jinja template and an empty favicon file. The last one exists because I want to avoid any error possible displayed in the network console of the browser. Everything else is content. - -You can find the site as a repository on my git. -
-A directory named blog contains all entries released as well as the ones I am working on. Metadata about subdirectories and the corresponding content is gathered inside a <key>:<value> structure. An entry is seen as valid and stored in the dictionary as soon as an index.html file is found. Who knows what might be added in the future. It will be added to a list of values. For now, metadata is solely the date of the blog articles. It is added to the RSS site automatically as well. The code snippet contains the dictionary.
-
-
-meta_data = {root[len("./templates/blog/"):] :
- datetime.fromtimestamp(os.path.getmtime(os.path.join(root,"index.html")))
- for root, dirs, files in os.walk("./templates/blog") if "index.html" in files}
-
-
-Routes are set by the use of decorators. The landing page is declared in the following snippet. After the dictionary is sorted by date, render_template() returns a string. The result will be interpreted by the browser in HTML/CSS format.
-
-
-@app.route('/')
-def index(_paths=meta_data):
- sorted_meta_data = dict(sorted(meta_data.items(), reverse=True, key=lambda item : item[1]))
- return render_template("index.html", _paths=sorted_meta_data)
-
-
-The main page, like every other page, extends the general jinja template. It contains a list of all articles found.
-
-
-{% extends "template.html" %}
-{% block head %}
- {{ super() }}
-{% endblock %}
-{% block content %}
- <p>Welcome to my website</p>
- <span class="index">
- {% for name,_date in _paths.items() %}
- <p><a href="{{ url_for('blog', blog_item=name) }}">{{ _date.date() }} {{ name }}</a></p>
- {% endfor %}
- </span>
-{% endblock %}
-
-
-URLs originate from the meta_data dictionary keys. These are the blog entries’ directory names. Flask’s url_for() returns the articles if you want to visit the site. It handles URL encoding as well. This is pretty neat since there are spaces in the names.
-
-
-@app.route('/blog/<blog_item>/index.html')
-def blog(blog_item, _date=meta_data):
- return render_template(f"blog/{blog_item}/index.html", _date=meta_data[blog_item])
-
-
-Digestif
--Incidentally, this turned out to be not only an opener for my blog but code documentation for myself as well. Maybe, I’ll need to pick it up in six months, who knows…. -As a closure, at least from my experience, the most feature-rich application seldom reaches its set goals. The one with a clear and precise target, fulfilling its minimal scope, most likely will. -
-This is how you make pesto, by the way. Bon Appetit! -
--
References
-[1] Less and More: The Design Ethos of Dieter Rams, 2015, ISBN:9783899555844-[2] Emotional Design: Why We Love (or Hate) Everyday Things, 2005, ISBN:9780465051366 -[3] The Design of Everyday Things, 2002, ISBN, 9780465067107 - - -{% endblock %} diff --git a/templates/blog/The Joy of One-Liners/index.html b/templates/blog/The Joy of One-Liners/index.html deleted file mode 100644 index 78a0e6f..0000000 --- a/templates/blog/The Joy of One-Liners/index.html +++ /dev/null @@ -1,85 +0,0 @@ - -{% extends "template.html" %} -{% block head %} - {{ super() }} -{% endblock %} -{% block content %} -{{ _date.date() }} -
The Joy of One-Liners
-There is an engineering idiom which withstands time like no other. As old as the hills but never forgotten. In informational technology relations, one could say it is ancient. Its dawn proclaimed from the shores of Seattle, defeated by an apocalyptic horseman with the melodious name NT. Shot! Point blank into the chest. Buried under the hills of an IT dark age which we call the nineties, dead. But is it? Well, not exactly. There is still life in the old dog. Like Beatrix Kiddo, it one-inch punches itself back to daylight. Coal black as a miner. Topsoil sticks to its beige 1978’s leather jacket, it trickles to the ground with every step taken to the nearest diner. The door opens again. “May I have a glass of water, please?” - --An art passed down from the ancestors. Its most visible interface: The Shell. Its name: The Unix Philosophy. -
-Coined by Doug McIlroy in the Bell System Technical Journal as a foreword to the UNIX Time-Sharing System. There is an even more concise version[1] and according to Eric Steven Raymond this is [2]: -
“This is the Unix philosophy: Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface.”- -
— Doug McIlroy —
-In some way, this is similar to the concept of the on vogue philosophy of microservices everywhere. Services are written to do one thing and do it well. They work together. Also, text is the connecting link between programs, services, and humans. The possibility to read a program’s output as text seems benign, as long as everything is working well. The advantage is interactivity at any time, testability of every component, and debuggability at every step of the process in an on the fly manner. Impromptu, out of reflex like a punch. -
-Pipe Dreams
--Mc Ilroy made another very important contribution, which is the Unix pipe. It is the practical implementation of connecting the programs inside the shell. He saw the programs as tools, plugged together via pipes building a toolbox. Program A’s
stdout is put into the stdin of program B. This leaves us with a single line of chained, well-defined programs to solve a problem that would otherwise be an extensive, multi-line program in any programming language of your choice.
-
-Let’s say we’ve got two programs. The first is one is fortune, the fortune cookie program from BSD games, which outputs random quotes as text. The second one is cowsay, which displays various kinds of animals as ASCII art. In order to work in a coherent manner a | is used. The pipe connects the first one to the second one.
--
-
-❯ fortune | cowsay
- _________________________________________
-/ Gil-galad was an Elven-king. Of him the \
-| harpers sadly sing: the last whose |
-| realm was fair and free between the |
-| Mountains and the Sea. |
-| |
-| His sword was long, his lance was keen, |
-| his shining helm afar was seen; the |
-| countless stars of heaven's field were |
-| mirrored in his silver shield. |
-| |
-| But long ago he rode away, and where he |
-| dwelleth none can say; for into |
-| darkness fell his star in Mordor where |
-| the shadows are. |
-| |
-\ -- J. R. R. Tolkien /
- -----------------------------------------
- \ ^__^
- \ (oo)\_______
- (__)\ )\/\
- ||----w |
- || ||
-
-
--To mix in some colors pipe everything through lolcat. Try it out! -
-
-
-❯ fortune | cowsay | lolcat
-
-
--So far so good, let us gain some real-world practice. -
-Punching Lines — Retire Your Password Generator
--Have you ever questioned the integrity of your one-click, GUI, proprietary password generator? Is its randomness really as unpredictable as it proclaims? Are you the only one which ends up knowing your generated password? There is a one-liner that ups your opsec instantly. Right from the source of randomness: -
-
-❯ head -n 42 /dev/urandom | tr -cd '[:alnum:]' | cut -c-12
-
-
-So, what is going on here? Everything is a file, that is the way *nix systems see it, even the device which puts out random data. To read the upper part of a file we use head. It will be sent to stdout and displayed via the shell. Parameter -n reads exactly 42 lines of the file given to gather enough randomness. The output of head will be sent to tr. In order to select only alphanumeric characters for our password, we use '[:alnum:]'. Parameters -c selects the complement of alphanumeric characters and -d deletes them. cut does exactly what it says, -c-12 cuts after 12 characters with leaves us with a random password of length 12. Every time you execute this one-liner a freshly made random password is returned.
-
-To extend the pool of possible symbols the manual of tr lists various sets of filtered symbols. In the case of a password generator, further sensible filters are '[:alpha:]' or '[:digit:]'. While '[:graph:]' is also viable in this case it returns one of the greater sets of symbols. Use it with caution, especially if you create passwords for database users. These might be terminated prematurely through ` or ' inside the returned string.
-
Sunday Punch
--This blog entrance can be seen as a prelude to a series of one-liners I use time and time again. The are multiple in the pipeline. One-liners should save you the time you otherwise would spend coding a complex solution. There is little better than solving a challenging problem in a single line. -
-
References
-[1] A Quarter Century of Unix, 1994, Peter Salus, ISBN:9780201547771-[2] The Art of UNIX Programming, 2003, Eric Raymond, ISBN:9780131429017
- -{% endblock %} diff --git a/templates/template.html b/templates/template.html index 2186b43..b5b7110 100644 --- a/templates/template.html +++ b/templates/template.html @@ -13,6 +13,7 @@