I don't think it's working for me (none of the keybinds work, and I don't see the fps counter). Brave, script-blocking disabled.
168 karma · joined January 5, 2018
If the in-person team doesn't like working remotely because they prefer to communicate and make decisions in-person, those conversations/decisions will have to be propagated to the remote team, for the company to function.
My gut feeling is that at some point, an important decision will be made in-person and not propagated, leading to confusion, lack of coordination, etc. Then, politics will ensue because the in-person team might feel like they're making concessions to the remote-team, and that the remote-team is always lagging behind, that the bulk of the decision-making responsibility are on the in-person team's shoulders, etc.
I'm 100% speculating, but I can see it happen.
It would be awesome to be able to record the notes to a sequencer, and then play them back, optionally sending via Web MIDI API[1], so that one could control an external synthesizer or VST.
[1]https://developer.mozilla.org/en-US/docs/Web/API/Web_MIDI_AP...
(not to fear-monger, just something to note)
Was there a first project you did that got you hooked?
---
Workspace 1 : browser(s)
Workspace 2 : code editor(s)
Workspace 9 : music library/mpv
Workspace 0 : signal
Scratchpad - : zoom
Scratchpad + : slack
Scratchpad [ : browser (front-end development)
Scratchpad ] : designs/notion/ChatGPT/etc
Scratchpad \ : terminal
---
What's your workflow?
=== Mastodon is a decentralized, open-source social networking service. It's often seen as an alternative to Twitter, more than Reddit. Here are some key points about Mastodon:
Decentralized Platform: Unlike traditional social media platforms, Mastodon is decentralized, meaning that it is split into numerous independent communities or servers (called "instances"), each hosted by different people or organizations. This decentralization allows more control for users over their online presence.
Open Source: Mastodon is open-source, which means its source code is available to everyone, and anyone can contribute to its development or adapt it to create their own version.
Content and Community: On Mastodon, you follow other users and can post "toots," which are like tweets on Twitter. There is a 500-character limit per toot. The content is generally more conversation-focused.
Privacy and Control: Mastodon provides a higher level of control over your posts and privacy settings. You can choose who sees your posts and can also content warnings to your posts.
---
Matrix, on the other hand, is an open-source project that provides an open standard for decentralized real-time communication, including instant messaging, VoIP (Voice over IP), and IoT (Internet of Things) communication. It's often seen as an alternative to Slack or Discord, more than Reddit. Key points about Matrix include:
Decentralized Communication: Matrix allows users to run their own communication servers, providing a greater degree of control and privacy. This is similar to Mastodon’s decentralization.
Interoperability: One of the defining features of Matrix is its ability to bridge, or interoperate, with other communication platforms, including IRC, Slack, Telegram, and Discord. This means that you can use Matrix to chat with people on these other platforms.
End-to-End Encryption: Matrix offers end-to-end encryption for communication, which ensures that only the people communicating can read the messages. This is not turned on by default but can be enabled for any conversation.
Versatility: Matrix can be used for a wide variety of communication needs, including instant messaging, voice and video calls, and even large scale chat rooms. It can support group communication better than Mastodon. ===
I noticed two issues:
1. The background image on the landing page doesn't load at all for me. I'm using Brave, with script-blocking disabled. If I manually inspect the page, and open one of the links behind the light/dark theme code, they load, but they don't seem to load on the page.
2. When I uploaded an image in a slide and went to full-screen mode, the image's borders are cut off (it's as if the image is zoomed in and the edges of the image are cropped). I believe it's the background-size: cover, and the aspect ratio of the image. Perhaps using background-size: contain would work?
I'll start working on a project, and if I run into something that feels wrong about the Doom Emacs default config/keybindings, I'll just open up a conversation with ChatGPT (the GPT-4 model, it's much better than 3.5).
I'll tell it that I'm using Doom Emacs, and then explain what I want, or what problem I'm having, and it will output code that I can try. It's not always correct on the first try, and sometimes I have to have a dialogue with it for a little while before it gets it right. Sometimes it struggles and begins to guess - and for those cases, I'll fall back to doing manual searches in Google, and if that fails, give up entirely and just write myself a TODO comment and keep marching forward.
It's help me set up config quickly that would've taken me a very long time to figure out.
I've been using ChatGPT (GPT-4) to help me write config (~1,000 lines of elisp code so far) and it's been very interesting/fun. I'm not going back.
At work, we use Svelte throughout our entire FE platform in many SPA micro-frontends, on both the web and mobile (w/ Cordova). We have 10,000+ daily active users. Our team has used Svelte in production for a few years. All of our developers learned it during the coding interview project, and on the job. It's fun and enjoyable to use.
I disagree strongly with this statement (not using it in production because of the reactive syntax). Reactive-blocks will trigger an update if their direct top-level dependencies change, not if one of their dependencies change from within a new scope/block (e.g. function-call) - that's all. Also, we only use reactive statements when we need to - we typically use data-binding instead.