40 Matching Annotations
  1. Jul 2021
  2. test-prof.evilmartians.io test-prof.evilmartians.io
    1. That technique works pretty good but requires us to use instance variables and define everything at once. Thus it's not easy to refactor existing tests which use let/let! instead.
    1. (This, incidentally, is why the current 'zero-config' marketing fad is such nonsense: it really means 'abdicate the responsibility for config'. Instead of a single place where you can view all the build config in a structured, coherent form, you have the exact same amount of config but scattered around your project in lots of annoying files that are harder to understand.)
  3. May 2021
    1. Note that not all of the colors in SMUI read from CSS variables, so some parts will still use the colors defined in the original Sass compile.
    1. Yeah, as many developers will tell you, designing/coding for email is an incredibly hit-or-miss proposition...this is simply one more thing that may work in some email clients. The only consistent behavior in HTML/CSS emails is that nothing is consistent. :-)
  4. Apr 2021
    1. It looks like touching objects "manually" versus "in cascade through belongs_to association" does not result in the same behavior.
    1. When we usedef self.method, though, we are defining a method across scopes: we are present in the regular class scope, but we use Ruby’s ability to define methods upon specific instances from anywhere; self within a class definition is the Class instance we are working on (i.e. the class itself). Therefore, usingdef self.method is a leap to another scope, and this feels wrong to me.
  5. Mar 2021
    1. Abbreviations used in bookkeeping

      so inconsistent!

      PL – Profit and loss; (or I/S – income statement) P/R - Payroll etc.

    1. These methods should be used with caution, however, because important business rules and application logic may be kept in callbacks. Bypassing them without understanding the potential implications may lead to invalid data.
  6. Feb 2021
    1. @conference_form.submit(conference_params)

      Surprised they called it submit, since that could imply that you're triggering an action called submit.

      They use other verbs to describe this:

      • sync
      • populate
      • write

      Analogous to Reform's sync / sync_models method.

      Actually, the name makes a lot of sense when you see it in context:

          @conference_form = ConferenceForm.new(conference)
          @conference_form.submit(conference_params)
      
          if @conference_form.save
      
  7. Jan 2021
    1. By default, menus open with an entrance animation. However, on desktop, menus can skip the animation and open instantly instead.

      Why only on desktop? That delay drives me crazy. I would like to skip on web/mobile too.

  8. Nov 2020
    1. The problem is that by default, module paths only work with things imported via npm because the new modules variable on resolve defaults to ["node_modules"]. This lets you import 3rd party code from npm really easily. But it means importing your code with a module path needs a config change.
    1. What bothers me most from Svelte: <!-- I want to bind the value of this custom input just like I would bind to normal input --> <input bind:value="query" /> <!-- works --> <search-input bind:value="query" /> <!-- doesn't work :/ -->

      I think this works in current Svelte

  9. Sep 2020
    1. Something to be aware of when you’re using any bundler: there’s very little consistency when it comes to how modules are packaged in NPM. It’s incredibly frustrating, especially considering many of us write modules these days using ESM. Here’s some various problems that come up:
  10. Aug 2020
    1. oh I'm fine with defective verbs. I'm not fine with inconsistency, though. Make it "Signup and login", and make it that on every SE page everywhere ever, and you can countin me.
    1. Where these systems most notably differ is in their units of volume. A US fluid ounce (fl oz), about 29.6 millilitres (ml), is slightly larger than the imperial fluid ounce (about 28.4 ml). However, as there are 16 US fl oz to a US pint and 20 imp fl oz per imperial pint, the imperial pint is about 20% larger. The same is true of quarts, gallons, etc.; six US gallons are a little less than five imperial gallons.
    1. On land, the league is most commonly defined as three miles, though the length of a mile could vary from place to place and depending on the era. At sea, a league is three nautical miles (3.452 miles; 5.556 kilometres).
  11. Jul 2020
    1. I do not understand why concat modify the array, as most of the method of the Array class has a ! method for that. Should I also introduced a concat! method?
  12. Jun 2020
    1. Is it “syncthing”, “Syncthing” or “SyncThing”?¶ It’s Syncthing, although the command and source repository is spelled syncthing so it may be referred to in that way as well. It’s definitely not SyncThing, even though the abbreviation st is used in some circumstances and file names.
  13. Apr 2020
    1. the spelling "Web site" (and the less questionable "web site") is an anachronism from the 1990s that is still in use by the NYT and some other conservative print media in the US while most others (including the online sections of the NYT!) today use "website".
  14. Mar 2020
    1. If you ever need to work with external translators, it’s a bit of a pain sending both your YML files and a bunch of views like index.en.html.erb. For one thing, you need some code to find all those files and send them, and put them back after receiving the translations. For another, your translator must respect the markup and code of the template, and know not to translate them. And if you want to use tools like WebTranslateIt, it’s easier to stick to YML.

      Good point. Better to store translations in your I18n backend in the same place as your subject translations, etc. (which by default is in YAML file).

  15. Dec 2019
  16. Sep 2019
  17. Mar 2017
    1. Der zweite Teil ist noch problematischer als der erste. Im Grunde betreiben die beiden mit dem zweiten Teil einen Etikettenschwindel: Sie schreiben "case study" drüber, weil das gut passt, ein Theorieteil und ein Fall. Aber was sie als Fallstudie verkaufen wollen ist alles andere, aber keine Studie. Für mich liest sich der zweite Teil wie eine Mischung aus Stadt(verwaltungs)marketing, Regierungsprogramm und Flugblatt einer idealistisch technophilen NGO. Analytisch und kritisch ist da nichts. In den Begrifflichkeiten lassen sich grundsätzliche Inkompatibilitäten zum ersten Teil finden (z.B. S. 35).

    2. Das Papier hantiert mit zwei Etiketten für die Stadt: neoliberal und rebellisch. Daraus ergibt sich ein Widerspruch, den es nicht weiter problematisiert oder gar bearbeitet: Sie wird als neoliberal etikettiert, soll aber dem datenbasierten Neoliberalismus 2.0 widerstehen (z.B. S. 23). Warum sie das tun sollte, wird nicht weiter erläutert, dass sie es nicht tut und dass das eben keinen Widerspruch bildet, fällt also auch nicht auf. Da ist die kritische Stadtsoziologie mit ihrem Konzept der "Unternehmerischen Stadt" analytisch klarer und erklärungsmächtiger.

    3. None   of   this   is   to   say   that,   somehow,   the   maker   movement   or   3D   printers   cannot   be  repurposed   to   serve   a   different

      Hinter der doppelten Verneinung in diesem Satz ist eine Aussage versteckt, die mehrere Jahrzehnte kritische Technologietheorie einfach so vom Tisch wischt: Technologie ist nicht neutral. Die Zwecke sind ihr eingeschrieben, nur ein sozialer und politischer Prozess der den Zweck der gesellschaftlichen Produktion adressiert kann auch Zweck und damit Charakter von Technologie verändern. Einfach "rumdrehen" lässt sich der Zweck von Technologie nicht.

      S. 24 heißt es übrigens m.E. schon sehr viel näher dran an einer angemessenen Sichtweise: "building hi-tech socialism using neoliberal infrastructure might very well be impossible."

    4. ature of many smart technologies: building hi-tech socialism using neoliberal infrastructure might very well be impossible.

      vgl. Anmerkung auf S. 21

    5. The idea was that technology would provide easy fixes to complex social problems while too often forgettingthe ultimate reason for the application of these technologies, which is serving the citizens and deliver better public services.

      Die Idee war also gut, nur bei der Umsetzung wurde was vergessen??! Das fällt ja nochmal meilenweit hinter die kritischen Bestimmungen des ersten Teils zurück. Bzw. zeigt, dass die beiden Teile wenig miteinander zu tun haben im Sinne einer kritisch-analytischen Textgenese, wie ich sie von einer Fallstudie mit vorangestelltem Theorieteil erwarten würde.

    6. for ordinary u

      "ordinary users" von airbnb sind also ok? da hätte ich ja auch noch mal diskussionsbedarf. und außerdem widerspricht es den schlussfolgerungen des eigenen papiers an anderer stelle (aufbau eigener infrastruktur).