tegiddrone

Came here to mention how slow and sometimes awkward ts-jest is. I'll have to try out Ava and the others. I think jest is a great asset over mocha/jasmine/sinon/chai but it gets awkward in the typescript realm. Also thinking about how since it really isn't type aware (especially for mocks) that it loses some points compared to the ecosystems like mockito, nsubstitute, etc.

Sometimes the meetings at $MEGACORP feel like useless ceremony. However I have worked with people who don't frikken read and do their own thing. For these people meetings are where you have to harvest their attention towards the cards/issues/wiki/specs/diagrams. Still not cool.

I think there is something worth cross examining. It's easier to relate to people when they are simplified. It's easier to be relatable when you are simplified. Since there is a social drive to relate with others being a trope has some reward.

The article discusses that the easy laugh takes priority over richer character development. Seems shallow, but it sells, just like being more easily relatable would sell.

It's an angle I don't pursue personally but I wonder if I should get into football or something just so I could relate with a larger population.

I want this for everything. So many times I go to text or email someone and then get distracted by the new messages in my inbox and forget what I was doing in the first place. It's especially bad on my phone where there might be cross-app notifications. Why did I pick up my phone again?

I appreciate your inquiry and articulation of your position. I agree that the homeless people you describe are in the direction of repulsive. I can give my answer to your question.

> "so the homeless there to me always seemed like they are homeless due to their own bad choices."

Contrary to your perspective, when I see a homeless person (or anyone) who is being unreasonable, hostile or indecent to me: I try to reflect that they did not have the resources and upbringing that allows them to be decent. I did not choose my upbringing therefore I did not choose my capacity to be a decent human being. It doesn't change them from being repulsive, but I begin to see how I could have been them if I didn't have the resources I had during my upbringing. Resources does not just imply financial capital, but also includes social capital (good relationships, family life), environmental capital (health, nutrition, safety.) So yes you can grow up "poor" (financially/materially) but become a decent human being. Your parents had good virtues instilled in them to not steal or do dodgy things.. I wonder who instilled those virtues in them? I'd like to thank them and make their practices ubiquitous.

Some rhetorical questions I ponder about:

Why am I a decent human being? Am I a decent human being? How much of my inherent decency is from underlying cultural fabric that I may be unaware of and take for granted? What I am doing do insure that I continue to be a decent human being?

.. do I have "blinders" on as the actor in the video suggests. What am I taking for granted that could be taken away? For all I know I could have a future medical condition that breaks me psychologically, or fall to some financial scam that puts me into ruin and I could become an indecent person. How do we create a society that makes it very difficult to become an indecent person? How do we create a society that protects everyone?

When I see an indecent homeless person: I see that society has failed them. Society might fail me too.

I think of the devs I've worked with that can't seem to manage a kanban board themselves or speak up and ask cross-cutting big picture questions.

If I know my senior dev doesn't give a shit, then I need to establish a manager/lead who does give a shit. If I have someone who does give a shit, then I have to spend less managing their shit.

It's pretty file dialog-y utilitarian but you can have it group by album/artist and also has a unified search through the library. I haven't explored its AutoDJ feature.

This looks nice! I am really interested in this space because I have a long build collection of mp3s and I'm not as interested in yielding to Spotify but I'm not always at the same computer or building for the accessibility.

Thus far I've been using mStream https://mstream.io/ with decent success. You can federate collections with your friends. My tries with NFS or SSHFS doesn't work reliably on windows/mobile hosts, especially across the (mobile) internet.

I know there is at least a few other projects in this space, some mentioned in the comments (Ampache.)

> "it’s charming in a way that only academic software can be."

I remember experiencing this as an undergraduate CS student with a bioinformatics research position. At the time I felt like I was too stupid to understand the code.

After I struggled with that, the professor reassigned me to making their software available for web use and wanted me to take over some PHP shell_exec rollercoaster for handling job submissions.

Your NSF funds hard at work.

The times I've done this in the past I've had to rely on buried forum posts or "hope for the best" with the linux installer options. Includes ambiguous reports on how encryption effects ssd wear/trim/etc.

I recently upgraded my laptop and stuck a new nmve ssd with hardware encryption features. It does have some security trade-offs but does protect decently against common theft and is hella convenient that it's all mostly managed in hardware beyond a pre-boot unlocker and a suspend-state kernel hack. Still had to dig deeeep into github issues to get it going in Linux. Works out of the box with Bitlocker allegedly.

Looks nice conceptually! I am getting a lot of jittery glitches with the graph dashboard and especially the CMS (unusable.) On FF 81.0.

I like Airtable for rapid prototyping and small data stores. It seems like this would be more comprehensive for that use case? Unclear on how to approach user login and permissions (of the project and not the canonic platform)

Yeah... isn't one benefit of a yubikey that a secret must be acquired by some very physical and intentional means? If my laptop/password is compromised, then they still can't log in because they need my secret token from the yubikey. Well, if having that secret token is just one curl call away if they're on the same network then its no longer a very physical and intentional safeguard.

I know... layers of unlikelihood.. but I'd probably opt for a physical "good button" gapped from my computer as sort of a closed electrical extension of my finger.

I begin to think about how to build a linter/scorecard for this sort of stuff.

Example linter rules:

  This article does not have a source.
  This article has no sources from a known resource [this community] find reputable.  
  This article has a source from a source known to this community to be non-reputable.
  This article has a "shallow" source such as a blog (tumblr, medium, blogspot, youtube)

Probably would need a mechanism to build/aggregate/crowdsource reputable source lists.

edit: formatting

On the other hand, other sorts of devs would probably not be entertained having to maintain a in-house database some unchained dev decided to introduce into the stack one day for "reasons." That tech debt will compound until it becomes more of a liability.. hopefully the product brings in enough money so that the in-house database can continue to be supported or removed.

This sort of stuff is what deters me from being a developer sometimes. Fuck the salary, get me out of here.

Nice. How to handle dead links? A growing problem with hyperlinking across sites in general.

An idea: when you take a quote, send the webpage through archivebox.io and pin the resulting artifacts to IPFS... or other repository the author can maintain. Key feature: the quoting author maintains the copy of the document they are quoting. The embedded "quote" fixture on the page will always point to the original URL and citation date alongside the author's "copy" of the page if it happens to die or change.

I like the simplicity! Some of the other options out there are pretty elaborate and not straightforward to get started.

One thing I'm always looking for in these is the docker run one liner. Because if I incorporate a tool into my work, how do I better ensure it's going to stay around by either pragmatic paid plan or OSS self host?

It's painful when I come to a project and the process for developing a feature is...

  (1) install database (or point to dev,) configure app, run seed data. 
  (2) creating the state in the database manually. 
  (3) change lines of code for feature
  (4) reloading app, navigating through to the feature state, manually verifying. 
  (5) fix runtime errors or bugs
  (6) Repeat as needed. Commit.

We don't need to swing around the entire stack to craft some pixels or make sure some message is displayed under specific circumstances. How do we get developers to think beyond this workflow?

I think TDD at the very least is a education/comprehension exercise in abstract thinking which will discourage scenarios like the one described above. Once someone is able to TDD and 'gets it' then sometimes the way they approach arranging code even without TDD is better. I think this is why we may have mixed messages like "TDD is great!.. but we don't practice it at work."

Using a test harness any sorts to test something in isolation will speed things up. We can better understand where a module begins and ends (i/o, side-effects.) Develop it rapidly in the harness and then a few (automated) integration tests at the end. It doesn't have to be a TDD-specific testing harness.

React Storybook is an example of a UI test harness. It's still manual testing, but we get that great separation-of-concerns goodness that makes for better designed (and easier to maintain) systems.