I'm struggling to find any information about this, either from Siedersleben or others, at least in English. Can you find any sources you can point me to?
Or, can you explain further? I'm not clear, for example, what you mean by "technical code."
And when you mention "the glue" are you talking mainly about APIs and protocols of all sorts (defined loosely)? This is where the edges of systems coincide and intended side effects reside.
Maybe I'm odd, but even having more experience with AWS, and even with the UI on AWS being superior, Azure's jargon and organization seems easier to learn than AWS.
If civic government contractors are anything like military contractors, then many of them haven't even heard of a version control system like Git or SVN – instead, naming file versions manually, like old Word DOC names (utils_b4_final2.cpp). I saw this personally at a major contractor in the last five years.
I don't have high expectations for the care invested in the code.
The bigger problem isn't being pwned in an embarrassing way like this. It's all the successful hacks into government systems which never get spotted or are never discussed at a level where they are likely to motivate positive change.
Yeah, I use DDG by default now, and only use Google for hard searches – and even then, I'm continually surprised by the frequency of terrible search results on Google these days.
I've been around to compare them all (and used to spend countless hours doing search engine research on Fravia's "web search lores" website).
Google represented a huge step up in search result quality generally. But in recent years, the quality has really slid – even while tuning results using more advanced Google features.
I don't think Google cares much about search result quality these days, except insofar as they have to keep a minimum threshold just to drive their ad and analytics revenue.
There is a lot of opportunity for other search engines to make strides forward in quality relative to Google these days.
One of the big differences is that at some point they seemed to basically delist forums, de-rank most blogs, and totally forgot that personal web pages still exist. All those things are still out there, but you are highly unlikely to find them via Google now. Maybe if you do an exact phrase search for the page's title, otherwise, they're buried.
Another is that they tried to get too helpful and it backfired. There used to be a bunch of search operators that you could use to be specific and most of them don't work anymore. Because that was too complicated for most people. So now instead Google just ignores what you searched for and tries to guess what you actually meant, and ends up showing a lot of irrelevant results, some of which don't match what you searched for at all.
The third is that nowadays almost always, Google tries to spin it into a commercial request. The top results are usually for e-commerce sites or something selling products or services, no matter what you search for. It always assumes you're trying to buy something, not trying to find information.
I switched to duckduckgo years ago, and it generally gives much better results, but even it seems to be slipping a bit now. Still way better than the modernized Google, but for how long?
Not saying this is what happened necessarily, but sometimes as a startup, you find yourself in a position where you must either sell to someone/anyone or the business must shut down (and you're left with the debt and with long-loyal early employees/friends whose equity you were never able to pay off).
I was a founding member of a social enterprise startup which ended up in a position very similar to that.
In our case, we were lucky that we had two options to sell: (A) to an investor who wanted to pervert our mission, vision, and values for profit; or, (B) to a nonprofit who didn't have the money to give us more than a single paycheck or two worth of payoff for our equity.
If we had sold to Option A, a dozen of us would be wealthy right now. But the company we built would have been perverted into something unrecognizable.
In our case, to our founder's credit, we sold to Option B to keep the dream alive, but none of us became wealthy... and the nonprofit just shut down the company we founded only 2 years after the purchase (partly because the nonprofit didn't have the business savvy to make it sustainable). _Everyone_ was just laid off.
That means, our noble sacrifice only extended the lifetime of our noble vision by 2 years, and we're certainly feeling less good about it.
Because the alternative would have meant that a bunch of us bleeding hearts would have the economic freedom right now to do all sorts of good for untold decades to come.
So I'm just saying, sometimes you don't get to have good options and everything sucks, no matter how well-intentioned you are.
On the other hand, Micro supports the Ctrl-based text nav/manip hotkeys (such as Ctrl-arrow, Ctrl-Backspace, CTRL-Home/End, also optionally combined with Shift for selection).
More of a DOS-origin set of hotkeys than GNU. So more familiar to some and less familiar to others.
It supports mouse interaction out-of-the-box, which is a big plus for some folks who haven't spent much time in keyboard navigation. The escape hatch is a nice option for some tasks, even for keyboard navigation pros.
All true, but the point at which web dev more generally moved to CSS over tables was considerably later, not least because early CSS was pretty hard to find resources on and work effectively with. Firebug helped a lot from 2005 on, as of course also the browser-native devtools it inspired, but in 2007 it remained far from a surprise to see sites built in what was then still a current, if not the latest, style.
I've become a big fan of using something like a `main()` function to act as the one conventional place where pure functions are piped together at the top of a module.
You get this very nice linear execution birds' eye view which tends to be readable. Combine that with hoisting and you start with this big picture at the top of a file, and then can dig deeper into the smaller functions as needed, written in lexical order lower in the file.
Here is a very trivial JS example from a kata:
```js
function main (numbers) {
return Array
.from(numbers)
.sort(byGreatest)
.slice(0, 2)
.reduce(toSum)
}
```
This is much more regularly written in languages with a pipeline operator, like Elixir, because you can pipe to arbitrary functions and operators (instead of being restricted to a method chain).
(JS/TS will get there eventually, if the TC39 committee can ever finally commit to the proposal.)
I like the method chain and find it very readable (and a good guarantor of typed output in the absence of strict types, if you use something like Typescript to lint it). But I don't see how the choice between that or a pipe operator has any impact on whether function main() should be your program's entry point. Unless your program is going to be an endless loop, e.g. a Nodejs server or else a game, I don't know why you'd want to saddle yourself with a main() every time it runs.
Or, can you explain further? I'm not clear, for example, what you mean by "technical code."
And when you mention "the glue" are you talking mainly about APIs and protocols of all sorts (defined loosely)? This is where the edges of systems coincide and intended side effects reside.