seletskiy

The novice asked: "Master, what is the advantage of unstructured text over structured? Is it not mere adoption?"

Master Git said nothing and pointed to the first shop, kept by the old scrooge Postgre.

As they entered, Master Git said quietly, shaping his mouth funnily:

  SELECT weight/2 FROM shelf WHERE name = ''

Next stood a shop kept by a bright newcomer, Duck D'Bee.

Master Git repeated:

  SELECT weight/2 FROM shelf WHERE name = ''

Their journey ended at a giant abandoned building beneath a dead neon sign: ORCL. The door stood open. Inside, putrid odour and dust lay upon deflated balloons and faded banners saying A.I. The shelves were still full of unmarked boxes.

Master Git shouted into the dark:

  SELECT weight/2 FROM shelf WHERE name = ''

  Now that my storehouse
  has burned down, nothing
  conceals the moon.

  Ever since my house burnt down,
  I see the moon more clearly

- Location search & display: no English version, only localized names, which is hard to reason if you don't know native language.

- Summary: a) what does precip. in % mean and how it correlates with cm? b) pressure is only displayed in hPa, while some countries prefer mmHg; c) what does ozone index mean and why is it important?

- Next 24 hours: visual indication for temp variation through the day would be easier to reason than just by looking at numbers (as discussed in TFA).

- Next 7 days: a) unnecessary precision for y-axis (e.g. 10.9°C vs. 11°C); b) band overshoot actual values (e.g. if I see 10..−10°C, I assume that would be max/min temp, but in fact it is 8..−9°C, which is impossible to tell without hovering mouse over); c) no horiz. line through 0°C; d) no horiz. lines through y-axis ticks, which makes it harder to reason about values closer to the end of the graph; e) precip. in cm tells little, especially when band is alike (0.00..0.80 cm) - peaks on graphs look like a lot, in fact they are not? g) seeing blue precip. graph subconsciously means 'rain' to me, while in fact it would be snow; f) labels for y-axis are at the same time very small, rotated 90° and also take too much horizontal space from the graph.

- Map: moving mouse over next 7 days graph causes time shown on map to change that would make sense if map's timeline would cover all 7 days, but it only covers small part of today.

- Week: a) fog icons look like they have solid white square background, which seems to be off compared to other icons; b) low/high values are hard to reason about, especially when it says 'Low … at 11am' and there is no tick labeled '11am' (10am .. 12pm) - displaying a line through coldest/warmest hours with °C value next to it would be much easier to understand.

Also: displaying air quality prediction based on last year's AQ would be helpful.

Practically speaking, I have no idea what I _personally_ can do except of accepting the inevitable.

There's nothing better for understanding something rather than trying to do that "something" from scratch yourself.

Why tighten the bolts on the airplane's door yourself if you can just outsource it somewhere cheaper (see Boeing crisis)?

Why design and test hundreds of physical and easy-to-use knobs in the car if you can just plug a touchscreen (see Tesla)?

Why write a couple of lines of code if you can just include an `is-odd` library (see bloated npm ecosystem)?

Why figure out how to solve a problem on your own if you can just copy-paste answer from somewhere else (see StackOverflow)?

Why invest time and effort into making a good TV if you can just strap Android OS on a questionable hardware (look in your own house)?

Why run and manage your project on a baremetal server if you can just rent Amazon DynamoDB (see your company)?

Why spend months to find and hire one good engineer if you can just hire ten mediocre ones (see any other company)?

Why spend years educating to identify a tumor on a MRI scans if you can just feed it to a machine learning algorithm (see your hospital)?

What more could I name?

In my take, which you can say is pessimistic, we already passed the peak of civilization as we know it. If we continue business as usual, things will continue to detiorate, more software will fail, more planes will crash, more people will be unemployed, more wars would be started. Yes, decent engineers (or any other decent specialists) will be likely a winners in a short term, but how the future would unfold when there will be less and less of them is a question I leave for the reader.

Can it be used to greatly simplify efforts by getting through boilerplate? — Yes.

Should the result be reviewed and proof-read by human? — Also yes.

---

Here subtle one: https://catalog.archives.gov/id/34384201?objectPage=40

Here is (one of) transcripts made by `o1-pro`:

  (2)

  …and I don’t know whether it can be reset for a
  date in December or not. Cornell seemed
  anxious that it should not come up too close to Christmas,
  and of course new suspicion [would be aroused?] [about?] him.
  I will take this up with the Judge as soon as I can get rid of the brief.
  Meanwhile I would like to know whether there is anything else
  in which I can be useful to you, since it behooves me
  in ways of uncomfortable relations with the present management.

  Are you going East in December?
  Has any word come from Hagerman?
  Were there any noteworthy developments at the hearings
  on the [Teapot?] trial?

  I have no inclination yet whether Wheeler will be wanted in
  Washington, but the chances are that he will not.

  With regards to all the brethren and [flock?], I am

  very sincerely yours,
  George A. H. Fraser

Somehow GPT-4o performs better on this example and fails only on "New Mexican practise" part.

  setInterval(() => { [...document.querySelectorAll(".upgrade,.loot-box-target,button")].map((e) => e.click()); }, 50)

Location: Armenia (UTC+4)

Remote: Yes (flexible working hours including US timezone)

Willing to relocate: Yes, preferably to country with high HDI

Technologies: technology agnostic. Boring and incomplete list of things I have worked with: frontend (React, Vue, Vite/Webpack, Typescript), backend (Go, Node, Python, Java, PHP, Erlang, Clojure), databases (PostgreSQL, MySQL/MariaDB, Redis, Memcached, ES, MongoDB), ops (Linux, *sh, K8s, Docker, VMs, IPMI, Zabbix, Grafana, Prometheus, Nginx, HAProxy, AWS, GCP, baremetal, on-call), ML (coding, [cross-]validating models, deploying, simulated envs), networks (all OSI levels), low-level (C, Ziglang, CUDA, assembly), hardware (MCUs, AVR, I²C, SPI, prototyping).

Résumé/CV: I have ~15 YoE and worked with a number of startups and projects, both as independent contractor and team leader. Check my GitHub to get rough overview: https://github.com/seletskiy and https://github.com/reconquest. Please contact me for more details.

Email: [email protected]

[1] https://github.com/seletskiy/dotfiles/blob/master/bin/piano

  Location: Armenia
  Remote: Yes, but flexible
  Willing to relocate: Yes, to a country with higher HDI
  Technologies: technology agnostic, everything from microelectronics to Web/GUI frontends
  Résumé/CV: on request, prefer 1:1 video chat
  Email: [email protected]

I would like to join biotech, med, eco, civil infra or aerospace projects that aim to tangibly reduce human and animal suffering and figuring out internal workings of Universe we live in.

Excel in small pragmatic teams with no bureaucracy. Able to provide optimized and highly reliable software.

Not interested in blockchain or GenAI projects.

There should be no death. For whatever reason, it is incredibly hard to find people thinking the same, despite, paradoxially no one wants to die.

Can we chat? My e-mail is in the profile.

I've been thinking about that for a quite awhile now, and I guess I have some perspective, but don't have exact answers and I don't think I can fit it into a HN message nor have enough motivation to do so.

_However_, I'll be more than glad to chat personally, maybe we can figure something out together. So, if you¹ want, drop me an e-mail. Address in profile.

--

¹) You, the topic starter or anyone reading this message who finds it relevant.

The code runs at steady rate of 18.00-18.40 GH/s at cloud GPU. In fact it's not hashes-per-second, but actually messages-per-second checked.

It launches a 64⁶ kernels in a loop, where each launch checks first two bytes of the SHA of a message concatenated with unique 6-byte nonce per kernel + 6-byte incremental nonce for each launch. There is only one block, so SHA algorithm is heavily trimmed. Also, most of the message is hard-coded, so pre-calculated SHA state is used; it's 10 loops less than needed to encode whole block. Since we only 2 bytes of the hash to check, last two loops also unrolled by hand to exclude parts that we wouldn't need. All code also in big-endian since SHA is, so message hardcoded in big-endian as well.

Base64-encoding is pretty time-consuming, so I've optimized it a bit by reordering the alphabet to be in ASCII-ascending order. I've got to the point where single binary-op optimization can earn 100-500 MH/s speed-up, and I don't really know what else here is remaining.

I don't have RTX4090, so instead I just rented 4090 GPU to run code on. It's less than $0.3 per hour.

I've tried GPT-4 to get some directions for optimization, but every single proposal was useless or straight wrong.

I by no means a C/GPU programmer, so probably it can be optimized much more by someone who more knowledgeable of CUDA.

GPU's are ridiculously fast. It freaks me out that I can compute >18,000,000,000 non-trivial function calls per second.

Anyways, if you want to chat, my e-mail is in the profile.

I've had the opportunity to test this in a clinical setting under an ECG. Not only did it increase my pulse, but it also caused the QRS complex to invert. Upon seeing this, the doctors advised me not to continue with this practice. However, I didn't experience any negative effects from this experiment. On the flip side, I haven't found any practical use for this ability either.

I would be intrigued to connect with someone else who has a similar capability. It seems that those internal "feelings" is as close to direct control as we can get.

As of pain, I have similar experience as well, except instead of detaching myself from the pain, I "look" as closely as I can. At a certain point pain decomposes to what it really is — electrical impulses, and from this point it literally starting to feel as electricity going through your body, quite the same feeling as if you accidentally grab both pins of the electrical plug, albeit not as intense.

Also, which approach you use to efficiently store and re-store relevant context information? I often find that intricate but important details are lost during context switch.

There is a very subtle mental state between "I am too aware that I am dreaming" and "there is no awareness of dreaming at all". I don't really know how to put it in words, but it seems that you BOTH need to supress part of the brain that wakes you up and prevent loosing awareness at the same time. It is very apparent during "ordinary" falling asleep, when you suddenly catch yourself that you are "seeing pictures" (hypnagogia phase) and become fully awake again. The trick is continue "falling asleep" without loosing awareness. Same applies during the lucid dream. You need to maintain balance.

You basically need to continue experimenting to notice those subtle changes to know which mental state would wake you up and which would not, so you'll get more precise control.

There are other factors at play for sure, like if you will manage to get your lucid dream right after first deep phase of sleep, your body would likely be not rested enough to quickly reach wakefulness, so you'll have more time.

I don't think that lucid dreaming is easy, and it was never easy for me. It was actually pretty hard work. It was almost impossible to get lucid dream if I was already mentally exhausted during the day. As soon as I stopped to practice, lucid dreams stopped too.

Maybe sound absurd, one technique that worked for me is to just "start spinning" around in your dream, so you can't focus on any specific part of the dream for a long time. Continuous attention to one detail in a dream somehow starts to breaking it apart.

One that worked for me is having a mechanical counter of some sort (like lap couter or just miniature code lock so you can use it as a counter), which you reset every morning and increment during the day every time after you ask yourself "Am I dreaming?" and doing some basic "reality check" (e.g. trying to breathe in through your nose when you pinch it, or checking clocks twice in a succession and validating that it makes sense, or just looking at your hands). The goal is to consistently do a number of reality checks during your waking life, which inevitably will increase the chance that you will do it in your dream. That will likely would cause you to wake up immediately for couple of times, but then you'll get used to it. It works simply because "if you don't ask yourself that you are dreaming during your waking life, what is the chance that you'll ask yourself it during sleep?".

There are number of other and more advanced techniques that borderline with "magic" to me, like falling asleep without loosing conciousness (and then waking up the same way), but I had this experience only a couple of times I guess.

In my judgment, the problem has been overstated. At the very least, with the 'tea,' it could be easily resolved by contacting me directly via e-mail, as mentioned in my GitHub profile.

I never intended for this code to be used by anyone else (there is no even a README file). But I'm delighted it helped someone attain their goals.

Anyway, I've stated that my code is MIT licensed.

I use double boot to host both Linux and Windows; when I need to use Windows, I just put Linux into hibernation. This greatly extends the amount of time it can go without being rebooted.

Driver and X problems still cropped up occasionally, but things seem much more reliable now than they did a while back.

This is a also the distro I'm familiar with from my time working on servers, where I've used it with ZFS with great success.

[1]: https://github.com/pwntester/octo.nvim