<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
    xmlns:wiki="http://purl.org/rss/1.0/modules/wiki/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:cc="http://web.resource.org/cc/"
    xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<docs>http://blogs.law.harvard.edu/tech/rss</docs>
<title>Marcin Borkowski: Homepage</title>
<link>https://mbork.pl/Homepage</link>
<atom:link href="https://mbork.pl?action=rss" rel="self" type="application/rss+xml" />
<description>Strona domowa Marcina Borkowskiego</description>
<pubDate>Mon, 20 Apr 2026 16:42:34 GMT</pubDate>
<lastBuildDate>Mon, 20 Apr 2026 16:42:34 GMT</lastBuildDate>
<generator>Oddmuse</generator>

<item>
<title>How to quickly generate the list of all columns in a PostgreSQL table</title>
<link>https://mbork.pl/2026-04-20_How_to_quickly_generate_the_list_of_all_columns_in_a_PostgreSQL_table</link>
<guid>https://mbork.pl/2026-04-20_How_to_quickly_generate_the_list_of_all_columns_in_a_PostgreSQL_table</guid>
<description>It is well-known that select * is an antipattern (except maybe in an SQL REPL). What to do, however, if you have a select * in your codebase and you want to change it to a proper list of column names?</description>
<pubDate>Mon, 20 Apr 2026 16:42:34 GMT</pubDate>
<comments>https://mbork.pl/Comments_on_2026-04-20_How_to_quickly_generate_the_list_of_all_columns_in_a_PostgreSQL_table</comments>
<dc:contributor>mbork</dc:contributor>
<wiki:status>new</wiki:status>
<wiki:importance>major</wiki:importance>
<wiki:version>1</wiki:version>
<wiki:history>https://mbork.pl?action=history;id=2026-04-20_How_to_quickly_generate_the_list_of_all_columns_in_a_PostgreSQL_table</wiki:history>
<wiki:diff>https://mbork.pl?action=browse;diff=1;id=2026-04-20_How_to_quickly_generate_the_list_of_all_columns_in_a_PostgreSQL_table</wiki:diff>
</item>

<item>
<title>Binding TAB in Dired to something useful</title>
<link>https://mbork.pl/2026-04-13_Binding_TAB_in_Dired_to_something_useful</link>
<guid>https://mbork.pl/2026-04-13_Binding_TAB_in_Dired_to_something_useful</guid>
<description>I’m old enough to remember Norton Commander for DOS. Despite that, I never used Midnight Commander nor Sunrise Commander – Dired is still my go-to file manager these days. In fact, Dired has a feature which seems to be inspired by NC: when there are two Dired windows, the default destination for copying, moving and symlinking is “the other” window. Surprisingly, another feature which would be natural in an orthodox file manager is absent from Dired</description>
<pubDate>Mon, 13 Apr 2026 18:56:07 GMT</pubDate>
<comments>https://mbork.pl/Comments_on_2026-04-13_Binding_TAB_in_Dired_to_something_useful</comments>
<dc:contributor>mbork</dc:contributor>
<wiki:status>new</wiki:status>
<wiki:importance>major</wiki:importance>
<wiki:version>1</wiki:version>
<wiki:history>https://mbork.pl?action=history;id=2026-04-13_Binding_TAB_in_Dired_to_something_useful</wiki:history>
<wiki:diff>https://mbork.pl?action=browse;diff=1;id=2026-04-13_Binding_TAB_in_Dired_to_something_useful</wiki:diff>
</item>

<item>
<title>Easter 2026</title>
<link>https://mbork.pl/2026-04-05_Easter_2026</link>
<guid>https://mbork.pl/2026-04-05_Easter_2026</guid>
<description>Christ has risen, rejoice! I have a bit of a rough time right now, but we have Good News – Jesus is greater than our troubles! Like in previous years, rest assured that I will pray a decade of the Rosary for all of you, my dear readers. Hallelujah!</description>
<pubDate>Sun, 05 Apr 2026 19:23:38 GMT</pubDate>
<comments>https://mbork.pl/Comments_on_2026-04-05_Easter_2026</comments>
<dc:contributor>mbork</dc:contributor>
<wiki:status>new</wiki:status>
<wiki:importance>major</wiki:importance>
<wiki:version>1</wiki:version>
<wiki:history>https://mbork.pl?action=history;id=2026-04-05_Easter_2026</wiki:history>
<wiki:diff>https://mbork.pl?action=browse;diff=1;id=2026-04-05_Easter_2026</wiki:diff>
</item>

<item>
<title>Node.js and .env files</title>
<link>https://mbork.pl/2026-03-30_Node.js_and_.env_files</link>
<guid>https://mbork.pl/2026-03-30_Node.js_and_.env_files</guid>
<description>The more I work with Node.js, the more I appreciate its built-in features. Supply chain attacks are a real thing and the more I can do without pulling in megabytes (or even kilobytes) of dependencies, the better. For example, one of the very common patterns in Node applications are configs in .env files. The traditional way to digest them is to use dotenv, which admittedly has zero dependencies – but nowadays even that is not necessary.</description>
<pubDate>Mon, 30 Mar 2026 12:44:27 GMT</pubDate>
<comments>https://mbork.pl/Comments_on_2026-03-30_Node.js_and_.env_files</comments>
<dc:contributor>mbork</dc:contributor>
<wiki:status>new</wiki:status>
<wiki:importance>major</wiki:importance>
<wiki:version>1</wiki:version>
<wiki:history>https://mbork.pl?action=history;id=2026-03-30_Node.js_and_.env_files</wiki:history>
<wiki:diff>https://mbork.pl?action=browse;diff=1;id=2026-03-30_Node.js_and_.env_files</wiki:diff>
</item>

<item>
<title>Disabling Eslint in one line with Tide</title>
<link>https://mbork.pl/2026-03-23_Disabling_Eslint_in_one_line_with_Tide</link>
<guid>https://mbork.pl/2026-03-23_Disabling_Eslint_in_one_line_with_Tide</guid>
<description>When coding in JavaScript, I use Eslint like everybody else. (Let’s set the discussion about Eslint vs. Oxlint for another time.) One problem I have is that sometimes (rarely, but not never) I need to tell Eslint that I broke one of the rules intentionally and I don’t want it to nag me about it.</description>
<pubDate>Mon, 23 Mar 2026 17:53:59 GMT</pubDate>
<comments>https://mbork.pl/Comments_on_2026-03-23_Disabling_Eslint_in_one_line_with_Tide</comments>
<dc:contributor>mbork</dc:contributor>
<wiki:status>new</wiki:status>
<wiki:importance>major</wiki:importance>
<wiki:version>1</wiki:version>
<wiki:history>https://mbork.pl?action=history;id=2026-03-23_Disabling_Eslint_in_one_line_with_Tide</wiki:history>
<wiki:diff>https://mbork.pl?action=browse;diff=1;id=2026-03-23_Disabling_Eslint_in_one_line_with_Tide</wiki:diff>
</item>
</channel>
</rss>
