1. 7
  1.  

  2. 10

    This is an Azure advertisement. If you are not interested in gluing APIs together with Azure you can skip it. Do not be mislead by the AI tag, the conclusion of the article links to the Azure AI service.

    Would be more amusingly titled: How many Azure services does it take to change a lightbulb?

    1. 13

      I just had to scroll 3 screens to get past a gigantic picture of a lamp in order to get to the text.

      What the fuck?

      Waiting on “How To Build A Blog Post That You Won’t Hate.”

      1. 7

        It’s Medium. Permanent huge bar across the top of the screen, permanent floating “open in app” button at the bottom.

        I don’t know how Medium makes web design decisions, but it’s certainly not with the user’s experience in mind.

        1. 1

          Or their UX data is based on small sample sizes rendering it almost useless.

        2. 4

          Waiting on “How To Build A Blog Post That You Won’t Hate.”

          1. The page should load text in under two seconds.
          2. The page should work if javascript is disabled or adblockers are enabled. There should be no popups or interruptions from the reading experience.
          3. Text should be the first thing you see. Both the title and at least some content should present without scrolling.
          4. All images must be directly relevant to the main text. If it does not clarify or expand on anything, leave it out. This means, among things, no memes, visual gags, or hero images. Most images will be screenshots or diagrams.
          5. All visual content must have alt defined for accessibility. If possible, none of the visual content should be necessary to understand the text. Assume you will have visually impaired readers and plan accordingly.
          6. All quotes and references should be linked, or at least cited. Use of tags should be consistent. You can decide what bold and italics mean, but monospace must mean code.
          7. Any javascript should only interact with the text to make it more comprehensible. Examples: interactive demos, collapsible elements, inlined footnotes. Apoexamples: select-to-share, “load more” buttons, background animations, any form of scrolljacking.

          Some of these might make the blog less marketable, but they’ll all make the blog more readable.

        3. 1

          At least Mac has the ‘Later’ button! In Ubuntu there is no way to force close a desktop notification. You just need to wait for it to go away. It’s infuriating.

          1. 1

            It’s better over in Xubuntu-land, with “Do not disturb” mode (and logging during dnd, or always if you prefer) https://simon.shimmerproject.org/2017/12/12/xfce4-notifyd-sees-a-new-point-release/

          2. 1

            Reposing my comment here for more engaging feedback: “One idea I’ve had for a while has been smart contextual notifications that take into account what you are doing and remind you if/when the work you do is somewhat related or at least when you’re procrastinating or resting. For example, you go to Amazon and a notification says “ah, you wanted to check this thing out a week ago remember?”. Or “oh you’re on Facebook, how about you answer that email…”. It’d need quite a bit of autonomy and AI of course, but that’s the gist of it.”

            1. 1

              That’s a cool idea. Regarding the “oh, you’re on facebook” thing, I use https://gist.github.com/unhammer/01c65597b5e6509b9eea to notify me about when long compiles complete, because I tend to alt-tab and forget about what I was doing when wait times get too long.

              But other than that I just use really dumb notifications that arbitrarily remind me of random TODO’s dredged up from the depths of my old notes.

              OTOH, I do make Emacs turn off very visible notifications (like from IRC etc.) during working hours.

              1. 2

                What do you use for notifications in Emacs? I use org mode, but have a bad habit of forgetting to check my agenda frequently enough.

                1. 3

                  For scheduled agenda items, I just use the built-in appt thing

                  (use-package appt
                      :config
                      (add-hook 'org-finalize-agenda-hook #'org-agenda-to-appt)
                      (appt-activate 1)
                      ;; Won't work without display-time:
                      (display-time))
                  

                  and to ensure it’s run at least once a day I have

                  (add-hook 'midnight-hook (defun my-org-agenda-on-midnight ()
                                             (org-agenda nil "p")
                                             (delete-other-windows)
                                             (org-agenda-goto-today)
                                             (recenter)))
                  

                  (which also means my agenda shows up in the morning)

                  But for other things I’ve started using https://github.com/jwiegley/alert (I could maybe get appt to use alert too, but haven’t bothered yet).

                  https://github.com/akhramov/org-wild-notifier.el might be relevant if you want more control (I haven’t tried it yet)