530 Matching Annotations
  1. Last 7 days
    1. Its not too complicated but it is an annoyance. I want /etc/hosts, /etc/resolv.conf, /etc/nsswitch.conf, /etc/rc.local and all the standard stuff to work. The heavy lifting is done in the kernel. All they need to do is leave it alone. Its getting harder to make Ubuntu behave like Linux.
  2. Jan 2021
    1. We also have an “anti-overtime” rate: past twenty hours a week, people can continue to work at an hourly rate of 50 percent. This allows us to have a high hourly rate for the highest leverage work and also allows people to work more per week if they wish.

      anti-overtime... love it.

    1. Most users frankly don’t care how software is packaged. They don’t understand the difference between deb / rpm / flatpak / snap. They just want a button that installs Spotify so they can listen to their music.
    2. Frankly, if the Ubuntu Desktop team “switch” from making a deb of Chromium to making a snap, I doubt they’d switch back. It’s a tremendous amount of work for developer(s) to maintain numerous debs across all supported releases. Maintaining a single snap is just practically and financially more sensible.
    3. This example of the chromium really shows that unless snaps or other similar format was used, applications would have to be sometime very heavily patched to work on older versions of systems to the point that it generates so much work that it would not be worth do to it otherwise, or at least not worth when the snap option exists and doesn’t require that much more work.
    4. What’s the use of ie. snap libreoffice if it can’t access documents on a samba server in my workplace ? Should I really re-organize years of storage and work in my office for being able to use snap ? A too high price to pay, for the moment.
    5. I - we all - totally agree about the benefits of snap for developers. But the loss of comfort and flexibility for end user is eventually a no-go option.
    6. Users want work be done. Not struggling about how allowing access to removable medias or such a file on another partition… Not breaking their habits or workflows each time a snap replaces a deb.
  3. Dec 2020
    1. People really don't stress enough the importance of enjoying what you're programming. It aids creativity, makes you a better teammate, and makes it significantly easier to enter a state of flow. It should be considered an important factor in choosing a web development framework (or lack thereof). Kudos!
    1. Making UIs with Svelte is a pleasure. Svelte’s aesthetics feel like a warm cozy blanket on the stormy web. This impacts everything — features, documentation, syntax, semantics, performance, framework internals, npm install size, the welcoming and helpful community attitude, and its collegial open development and RFCs — it all oozes good taste. Its API is tight, powerful, and good looking — I’d point to actions and stores to support this praise, but really, the whole is what feels so good. The aesthetics of underlying technologies have a way of leaking into the end user experience.
    1. And then it will help you choose a specialization in the field that you like.
    2. Find Your Passion, Then Monetize It The
    3. Try a little of everything, and then choose a specialization. Money is not the most important thing. You need to LOVE your activity! But you don't know what you like until you try it.
  4. Nov 2020
    1. Microbundle also outputs a modern bundle specially designed to work in all modern browsers. This bundle preserves most modern JS features when compiling your code, but ensures the result runs in 90% of web browsers without needing to be transpiled. Specifically, it uses preset-modules to target the set of browsers that support <script type="module"> - that allows syntax like async/await, tagged templates, arrow functions, destructured and rest parameters, etc. The result is generally smaller and faster to execute than the esm bundle
    1. The use of __proto__ is controversial and discouraged. It was never originally included in the ECMAScript language spec, but modern browsers implemented it anyway. Only recently was the __proto__ property standardized by the ECMAScript 2015 specification for compatibility with web browsers, so it will be supported into the future.
    1. Since I closed down the Dish, my bloggy website, five years ago, after 15 years of daily blogging, I have not missed the insane work hours that all but broke my health.
    1. Throughput in Planned vs Unplanned Work: The graph to the left is even more interesting as it contains the initial hints at what’s actually happening. That graph measures throughput with an emphasize on unplanned work. Now, what’s unplanned work? Typically, everything related to features or improvements is planned, whereas bugs, re-work, and service interruptions are unplanned. Let’s see why unplanned work is relevant.

      [[throughput]] - [[planned work]] [[unplanned work]] - what things fall under planned and unplanned, and how are they impacting things?

    1. I've only done components that need to/can be Svelte-ified. For some things, like RTL and layout grid, you can just use the MDC packages.
    2. This is Sass based, and therefore doesn't require Svelte components

      Just because we could make Svelte wrapper components for each Material typography [thing], doesn't mean we should.

      Compare:

      • material-ui [react] did make wrapper components for typography.

        • But why did they? Is there a technical reason why they couldn't just do what svelte-material-ui did (as in, something technical that Svelte empowers/allows?), or did they just not consider it?
      • svelte-material-ui did not.

        • And they were probably wise to not do so. Just reuse the existing work from the Material team so that there's less work for you to keep in sync and less chance of divergence.
    1. anything that makes you lighter helps create the balance which keeps you going.

      "In order to balance I never left anything pending on my to-do-list for tomorrow. If I did, I worked on break shift from home post putting her off to sleep. This was possible because I could manage my office on laptop. To release the pressure points I tore papers, took cold water bath in the middle of the night, laid on the floor in child pose." Monica Suri

  5. Oct 2020
    1. Please don't copy answers to multiple questions; this is the same as your answer to a similar question

      Why on earth not? There's nothing wrong with reusing the same answer if it can work for multiple questions. That's called being efficient. It would be stupid to write a new answer from scratch when you already have one that can work very well and fits the question very well.

    1. Focus on your application: forget about forms details like I'm dirty, field touched...
    2. You can try to build a solution to tackle these issues on your own, but it will cost you time and money... why not use a battle-tested solution to handle all this complexity?
    3. If you want to implement a form with a superb User Experience, you have to take care of many variables:
    4. Form validation can get complex (synchronous validations, asynchronous validations, record validations, field validations, internationalization, schemas definitions...). To cope with these challenges we will leverage this into Fonk and Fonk Final Form adaptor for a React Final Form seamless integration.
    5. Managing Form State (holding field information, check if a control has been touched, if the user has clicked the submit button, who owns the current focus...) can be tedious and prone to errors. We can get help from React Final Form to handle these challenges for us.
    1. This implementation is based upon following sources: JavaScript Debounce Function by David Walsh Lodash implementation
    1. Other frameworks, which use a template syntax built atop HTML — Svelte, Vue, Ractive, Glimmer etc — have historically been fragmented, meaning those tools need to be reinvented many times.
    1. "Protestant" life of wealth and risk over the "Catholic" path of poverty and security.[8]

      Is this simply a restatement of the idea that most of "the interesting things" happen at the border or edge of chaos? The Catholic ethic is firmly inside the stable arena while that of the Protestant ethic is pushing the boundaries.

    1. Almost every social network of note had an early signature proof of work hurdle. For Facebook it was posting some witty text-based status update. For Instagram, it was posting an interesting square photo. For Vine, an entertaining 6-second video. For Twitter, it was writing an amusing bit of text of 140 characters or fewer. Pinterest? Pinning a compelling photo. You can likely derive the proof of work for other networks like Quora and Reddit and Twitch and so on. Successful social networks don't pose trick questions at the start, it’s usually clear what they want from you.

      And this is likely the reason that the longer form blogs never went out of style in areas of higher education where people are still posting long form content. This "proof of work" is something they ultimately end up using in other areas.

      Jessifer example of three part post written for a journal that was later put back into long form for publication.

    1. I’ve written for 15 years, 569 essays, and 2.9 million words and counting. You can read a quick intro or my best work, which I curate below.
  6. Sep 2020
    1. export let client; setContext("client", client);

      Wouldn't this set context to undefined initially? And reassigning a new value to client wouldn't update the value stored in the context, would it? It would only update the let client variable.

      Where does this let client actually get set to the client from async function preload? I guess I need to understand Sapper more to know how this works, but it doesn't seem like it could.

      Update: I think I found the answer (it runs before):

      https://hyp.is/3aHeJgNFEeunkCsh8FVbDQ/sapper.svelte.dev/docs/

      It lives in a context="module" script — see the tutorial — because it's not part of the component instance itself; instead, it runs before the component is created, allowing you to avoid flashes while data is fetched.

    1. This leads to web developers at every company needing to rebuild every control from scratch. This represents millions of dollars of investment for each company to duplicate work that many other companies are also doing.
    2. Modern view libraries like React allow teams to build and maintain these components more easily than ever before, but it is still extraordinarily difficult to do so in a fully accessible way with interactions that work across many types of devices.
    1. It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
    1. There’s a lot of value in slow thinking. You use the non-lizard side of your brain. You make more deliberate decisions. You prioritize design over instant gratification. You can “check” your gut instincts and validate your hypothesis before incurring mountains of technical debt.

      Slow thinking is vergelijkbaar met Deep Work.

    1. If ADHD is not a disorder, but a mismatch with a human environment, then suddenly it’s not a medical issue. It’s an issue for educational reform.

      How can this impact #[[Adult ADHD]] and #[[ADHD at work]]

    1. Thus could Ken Copeland write in his Laws of Prosperity, "Do you want a hundredfold return on your money? Give and let God multiply it back to you. No bank in the world offers this kind of return! Praise the Lord!” In this mentality, tithing is a financially responsible thing to do. It’s a show of faith and a shrewd investment alike, a wager on the idea that God acts in the here and now to reward those with both faith and a sufficiently developed work ethic.

      And of course, if you're giving away 10%, you've got to work even harder to make up that initial loss!

  7. Aug 2020
    1. Our company is remote-first and will always be open to employees to work anywhere in the U.S. (or the occasional trip abroad). We made this decision with a great deal of intention because we believe creating and nurturing a remote culture is a key to inclusion.

      As we've been adjusting to the pandemic and going remote, I have been thinking about the differences between

      • [[remote only]]
      • [[remote first]]
      • [[remote friendly]]
    1. Ohhh, never thought of this hypothesis: that the act of getting drunk together might be a social technology that helps us verify the trustworthiness of others by inhibiting their higher cognitive functions and thus making it harder to consciously fake things.

      Proof of trustworthiness

    1. having a completely distributed team can make it very difficult for team members to get to know each other on a personal level

      There is lots that gets missed from the chance encounters of in-person interactions.

      I've found this to be a challenge when onboarding at a new company.

      Many of the ways we happen to meet people in a normal office environment can go away, the chance encounters need to become intentional ones.

      It can feel awkward reaching out to someone over slack to ask for something if you have never had any kind of casual conversation or interaction with them before.

    1. Brynjolfsson, E., Horton, J. J., Ozimek, A., Rock, D., Sharma, G., & TuYe, H.-Y. (2020). COVID-19 and Remote Work: An Early Look at US Data (Working Paper No. 27344; Working Paper Series). National Bureau of Economic Research. https://doi.org/10.3386/w27344

  8. covid-19.iza.org covid-19.iza.org