-
Notifications
You must be signed in to change notification settings - Fork 1
/
index.html
207 lines (193 loc) · 9.09 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Recollection</title>
<link rel="shortcut icon" href="/favicon.ico" />
<link href="/feed.xml" type="application/atom+xml" rel="alternate" title="Recollection Atom Feed" />
<link rel="stylesheet" href="/theme/css/screen.css" type="text/css" />
<link rel="stylesheet" href="/theme/css/pygments.css" type="text/css" />
</head>
<body>
<div id="header">
<div id="nav"> <div class="selected">
<a href="/">Home</a>
</div>
<div>
<a href="https://heptapod.host/saaj">Code</a>
</div>
<div>
<a href="/archive.html">Archive</a>
</div>
</div>
<div class="header-box">
<h1><a href="/">Recollection</a></h1>
</div>
</div>
<div id="wrapper">
<div id="content"> <h4 class="date">Apr 15 2018</h4>
<div class="post">
<h2 class="title">
<a href="/article/developer-friendly-job-search-the-tooling.html" rel="bookmark" title="Permanent Link to Developer-friendly job search. The tooling">
Developer-friendly job search. The tooling
</a>
</h2>
<p>It is quite interesting to me to see how software job market works in the Netherlands
from an active candidate’s point of view. Unfortunately one great journey has almost
ended and there is a firm incentive to find something at least as good. Having my
current job through StackOverflow Jobs, I intended to keep using what proved to work,
like marking the profile active, entering <tt class="docutils literal">python <span class="pre">-django</span> <span class="pre">-sysadmin</span></tt> into the search
field, adding relevant filters and subscribing to the search. That, as such, of course
works, but it looks it is not the most popular software talent recruitment service
that Dutch companies use. And many companies are still quite happy to pay 20% of the
gross year salary per new hire to the volume-oriented keyword-matching salesmen,
colloquially referred as recruiters.</p>
<div class="readmore"><a href="/article/developer-friendly-job-search-the-tooling.html">Read more</a></div>
<div class="clear"></div>
<div class="info">
<a href="/tag/python.html" class="tags">
python
</a>
<a href="/tag/asyncio.html" class="tags">
asyncio
</a>
<a href="/tag/browser-automation.html" class="tags">
browser-automation
</a>
<a href="/tag/sqlite.html" class="tags">
sqlite
</a>
<a href="/tag/full-text-search.html" class="tags">
full-text-search
</a>
<a href="/tag/document-storage.html" class="tags">
document-storage
</a> </div>
</div>
<div class="clear"></div>
<h4 class="date">Apr 23 2015</h4>
<div class="post">
<h2 class="title">
<a href="/article/cherrypy-questions-testing-ssl-and-docker.html" rel="bookmark" title="Permanent Link to CherryPy questions: testing, SSL and Docker">
CherryPy questions: testing, <span class="caps">SSL</span> and Docker
</a>
</h2>
<p>Basically this is a CherryPy work-in-progress article. However, it aims to draw the line
with testing infrastructure I was working on, as it seems to be completed. The article
covers what has been done and what issues I met along the way of reviving the test suite
to serve its purpose. The way is not traversed fully of course and there’s a lot left to
do. It also seeks to justify concerns about CherryPy <span class="caps">SSL</span> functionality’s correctness and
viability. As well, it tries to answer appeared questions about official Docker image and
its range of application.</p>
<div class="readmore"><a href="/article/cherrypy-questions-testing-ssl-and-docker.html">Read more</a></div>
<div class="clear"></div>
<div class="info">
<a href="/tag/cherrypy.html" class="tags">
cherrypy
</a>
<a href="/tag/python.html" class="tags">
python
</a>
<a href="/tag/testing.html" class="tags">
testing
</a>
<a href="/tag/ssl.html" class="tags">
ssl
</a>
<a href="/tag/docker.html" class="tags">
docker
</a> </div>
</div>
<div class="clear"></div>
<h4 class="date">Jan 25 2015</h4>
<div class="post">
<h2 class="title">
<a href="/article/future-of-cherrypy-bright-and-shiny.html" rel="bookmark" title="Permanent Link to Future of CherryPy: bright and shiny?">
Future of CherryPy: bright and shiny?
</a>
</h2>
<p>First off, I really hope so, tough at the same time I see the reasons for it. Moreover
I have been trying to contribute back to the community by giving knowledge that could hopefully
cut the rough edges that I’ve met on my way of learning and employing CherryPy [1]. And when
CherryPy is calling, I have something to say.</p>
<p>This article is my consideration in reply to the holiday post [2] by Sylvain Hellegouarch
in CherryPy user group about its current state and future, which recalls to older big
discussion [3] about the status of development of CherryPy.</p>
<div class="readmore"><a href="/article/future-of-cherrypy-bright-and-shiny.html">Read more</a></div>
<div class="clear"></div>
<div class="info">
<a href="/tag/cherrypy.html" class="tags">
cherrypy
</a>
<a href="/tag/python.html" class="tags">
python
</a>
<a href="/tag/future.html" class="tags">
future
</a> </div>
</div>
<div class="clear"></div>
<h4 class="date">Dec 08 2014</h4>
<div class="post">
<h2 class="title">
<a href="/article/qooxdoo-next-and-targeting-website-development.html" rel="bookmark" title="Permanent Link to Qooxdoo “next” and targeting website development">
Qooxdoo “next” and targeting website development
</a>
</h2>
<p>Initially, this post was meant to be an open letter to Martin Wittemann, an urge to do not break the only
robust and consistent JavaScript development environment, in sense of bug #8618 [1]. How robust and
consistent? Most importantly it is about:</p>
<ul class="simple">
<li>Code structure: modern feature-rich object model with properties, events, interfaces, mixins and more,
namespace tree, data-binding,</li>
<li>Dependency management: automatic and transparent dependency resolution, component packaging,</li>
<li>Deployment: code optimisation, single- and multi-part builds,</li>
<li>Standard library: i18n, <span class="caps">CLDR</span>, high level <span class="caps">BOM</span> <span class="caps">API</span>, normalised events, normalised ECMAScript, test
infrastructure, <span class="caps">API</span> documentation, feature detection.</li>
</ul>
<p>All this comes out-of-the-box, builds layer on layer, is seamlessly integrated and handed to an end developer
on a silver platter. The codebase is one of the best quality I have ever seen. It is readable,
comprehensible, possible to extend, and is a huge a knowledge resource per se. And note, I am talking about
tools and environment, not <span class="caps">UI</span>. Like former Qooxdoo developer, Fabian Jakobs, stated in one of his
presentations [2]:</p>
<blockquote>
Don’t just look at the widgets, look at the development tools as well.</blockquote>
<p>Luckily, as was recently stated in <em>Website fundamentals: next challenges</em> [3], the “next” (branch and then a
separate repo [4]; later referenced Next) turned out to be a experimental website-oriented fork of Qooxdoo,
which doesn’t mean to be merged back to Qooxdoo. At least any time soon. Panic is soothed, impending doom
doesn’t overhang the good times. It’s time to dissect and discuss.</p>
<div class="readmore"><a href="/article/qooxdoo-next-and-targeting-website-development.html">Read more</a></div>
<div class="clear"></div>
<div class="info">
<a href="/tag/qooxdoo.html" class="tags">
qooxdoo
</a>
<a href="/tag/javascript.html" class="tags">
javascript
</a>
<a href="/tag/future.html" class="tags">
future
</a> </div>
</div>
<div class="clear"></div>
<div class="clear"></div>
<div id="footer">
<p>
Powered by <a href="http://getpelican.com/">Pelican</a>
· <a href="/feed.xml" rel="alternate">Atom Feed</a>
</p>
</div>
</div>
<div class="clear"></div>
</div>
<script type="text/javascript">
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
})(window,document,'script','//www.google-analytics.com/analytics.js','ga');
ga('create', 'UA-29858354-12', 'auto');
ga('send', 'pageview');
</script>
</body>
</html>