haddr

I had an opposite experience: solr was rock solid and didn’t require too much maintenance.

The rest is only hallucination from malnutrition and death

Oh, press alt when minimising/maximising a window for an additional surprise.

Press Cmd to reveal the path

And when you are in terminal and want to change dir to some different path, just drag and drop it from finder (either a file or just a icon from the title bar)

where actually the best happens in the comments under hn submission to this article (in short: the claim seems not valid for certain domains)

Somehow reminds me of the "Typeset in the future" serie of movie analyses from the perspective of typography used.

Highly enjoyable (if you like typography and sci-fi movies): https://typesetinthefuture.com/2016/06/19/bladerunner/

I totally understand, in our setup, flaky tests happen when testing parts of the software that depend on the Hadoop infrastructure. Sometimes you can’t fully control some pieces and as a result those tests can be flaky.

However I want to highlight how frustrating it is when your tests fail when you wait for the build to finish...

Had some second hand opinions on running NiFi in prod and all of them were rather negative, some saying it was a mistake. That was around one year ago. I wonder if things have changed since then.

still, after changing the get_scale, fonts doesn't look like they are rendered in higher resolution.

There should be a separate feature to handle higher-resolution screens.

Anyway, it feels really easy to change anything in this editor.

same here, works on mac quite nice :) and it's super fast.

also fonts are a bit big on retina screen.

I enjoy reading proceedings from SIGBOVIK :)

http://sigbovik.org/2020/proceedings.pdf

I was using Evolution on daily basis at work (around 2015-17) but I switched quickly to Thunderbird due to stability issues. I was using Evolution primarily for its support for Exchange Server, but it wasn't very stable at the time. On the other hand, the same was possible in Thunderbird through a very solid proprietary plugin (exQuilla).

iSH is another good alternative, with alpine Linux and possibility to install packages. Still in beta though

we had to setup a simple linux for the purpose of diplsaying some stats on the attached screen. choices were: debian and nixos. debian would take approx half day to setup (given other project tasks). nix os was chosen and it took 2 weeks and now it is rather hard for non-nix user to fix anything.

No it is usually not the case.

There is a real difference between declarative and imperative approach to configuration and such decisions can be traced in many projects.

Simplifying things: declarative configuration is usually the best approach if you manage to capture most of your component behaviour in some relatively simple language with limited expressivity.

Imperative is where you start mixing some code in. This is usually because of big amount of corner cases and where flexibility is a must. This is seen quite often in build tools: it’s hard to just configure everything, some projects need to be built using really custom pipelines.

Some time ago I wrote an answer on stackoverflow: https://stackoverflow.com/questions/38947884/changing-proxy-...

Maybe that can help.

Another way to say that "the limits of my language mean the limits of my world" (Wittgenstein). It is so true on many levels.

Open source it (if that's possible), let's figure out if there is community who would see value in it!

Same here: I'm taking a lot of notes and find SimpleNote/Notepad++/NV work for me for note taking but not for note management. And I also build several tools to manage it. For now I use very simple full-text search (qgrep) and fzf (with my own modifications) to perform search-as-you-type to find notes/source code. qgrep is good for really quick index and it has incremental indexing that works for my byt i'm hitting some problems as it works good for code search but not so good for notes. However i don't feel like using anything that start a server. I just don't think I have that many notes.

Actually all those hubs are almost all equal: they support usb 3.0 and differ very little. Just buy Anker (upgraded) and you will be fine. Different story for usb 3.1 gen 2. There’s only one hub currently and it’s Sony UHS-II. (And even this one can support 4K only in 30 FPS)

I think Brooks is still right and what author mentions is not one thing but a set of practices that became proven enough that became almost like a standard approach in software development. And they provide some productivity gains if we compare how software was built 50 years ago. Yes, the difference is big but we forget that all those things were introduced incrementally and in the course of decades. So yes, together they make a huge difference but they haven’t appeared in one day.

Jena API was quite common to use with Java, and RDFLib for python.

I wonder if there is something for CRUD as easy as Delphi used to be for rapid prototyping.

Original article doesn't say anything about "database join". It's about joining two datasets by some common ID.

R in this case fits the bill and even allows for some relational algebra here (e.g. INNER JOIN would be merge(X, Y, all=FALSE), LEFT OUTER JOIN: merge(X, Y, all.x=TRUE), etc...)

In R this is rather straightforward, and you can also achieve it without additional libraries:

  weight <- read.csv("weight.csv")
  person <- read.csv("person.csv")
  merge(weight, person, all=TRUE)

Of course, nowadays you would use data.table, but still the merging logic would be exactly the same.

All are in public domain now. Read the one i mentioned as it is shorter read. If you like it then go of the other one.

Command Line tools are powerful beasts (e.g. awk) and they were always central to data preprocessing. But do we need to call it now a data science?

Read Schopenhauer „The Art of Being Right: 38 Ways to Win an Argument”. It’s a short read, but mind opening if you’re new to the subject. If it seems too long then just read some shortened version. If you still have some time after that then go to “list of cognitive biases” Wikipedia entry and continue there.

I believe it is crucial to understand what tricks others are using in arguments. And also what’s our cognitive limits and logical fallacies when trying to understand the world.

I was always looking forward to something like that, since at least 15 years. Today's minds are shaped by what we read online and this is our source of knowledge on many topics (apart from books and other media), so why not organizing it? But then I noticed that this would add another source of data to be managed, evolved, etc, and today I'm more thinking that it's more about being organized as an individual rather than simply relying on just another tool for that.

Anyway I will give it a spin! Looks like a good piece of work.