tetsuhamu

They're still around.

If you can't find the kind you're looking for, you can make one!

Oh dang, that's neat! Thank you!

It's not actually a single binary.

It's a single binary working with the filesystem.

All content is on the filesystem.

The "single binary" is a lightweight golang webserver that serves content from the filesystem.

I agree wholeheartedly with all of the points made in the article, but this website kinda sucks as an example.

- The website is "one binary", but the deploy strategy involves compiling it instead of running a binary artifact

- Won't rely on github pages, but depends on external resource at openlibrary.org

- Writing your own stuff lets you take advantage of open standards, but the .html files in thoughts/ are structured as plaintext with a false file extension

- When people go this route, they usually try to cram everything into the initial page load. This has several static files served dynamically.

- The Golang code does not cache any responses, and does not store templates in memory.

- Several dependencies in the go.mod file, all of them seem unused?

Most importantly: No discussion about the technical benefits of the "single-binary" ethos compared to modern infrastructure.

It's my humble opinion that it's a great idea, and this is a poor example.

That's why it's awesome.

Lol all these people salty at you.

I think you're right that the world of executives is less like "employment" and it's kind of insulting to pretend it is.

But I also think it's fine for executives to sue the companies they represent. I think the government should have a role in corporate governance. I would even support having a government appointed representative like the Federal Reserve has.

But I'm just a communist :p

These things are made of neural networks. Literally everything about them is weights and biases.

I agree and all, but it's weird to claim these models have general bias without testing them on a variety of inputs. These models have a lot of minute details. They're capable of differentiating a lot of specific things. They don't lack information about Indian women.

The industry agreed to standardize on Python for the task of describing compute-graphs that get executed by compute engines implemented in something other than Python. Python is not meant to be used for the computation itself.

It seems to be failing to create a repository right now

Defund and Re-allocate. They really need to start saying the re-allocate part. No one can take them seriously without it.

Dude was literally petitioning his government for a redress of grievances, at a public meeting exclusively meant for that.

I get your point, and I agree with it for most cryptocurrencies.

In this case, the proof-of-work would be peer-review instead of computation, and the "blocks" would be as frequent as "minor releases". The need for computation would be pretty light.

Not that I'd actually support it in practice lol

if you load an image from imgur.com, you could also upload to several other users, and pay for the bandwidth and battery loss yourself!

They sometimes pay for traffic out of their network. And sometimes companies pay them to host caches.

no one uses ipfs:// URLs in HTML

that was so embarrassing to read

Yes!

We build walls out of materials opaque to visible light. Our walls are basically windows for wifi, so make them opaque! It's all EMR

Quick google search:

37.12 billion metric tons of CO2 currently released per year

https://www.statista.com/statistics/276629/global-co2-emissi....

This. It's an empty promise.

Ruby lends itself to a certain kind of "decomposition" or "factoring".

In a functional programming language, you get a "functional decomposition". In an OOP language, you get an "object decomposition". It's what your program structure looks like.

Ruby supports those things, but IMHO provides a sort of "grammar decomposition". Writing programs and libraries in Ruby tend to look like writing new programming languages.

Python tends to produce a "practical decomposition", or a procedural decomposition. Yeah, you can make classes and functions, but actually doing things is valued more than structuring things.

Location: San Francisco

Remote: No

Willing to relocate: No

Technologies: Full stack, RoR, Django, Flask, Golang, Java, Python, Kubernetes, AWS, SQL, Mongo, Kafka

Resume/CV: https://www.linkedin.com/in/danielrobertlewis2/

Email: daniel.robert.lewis@gmail.com

Yes, I have. No, it's not normal. Yes, it "just happens" to some people, where "some people" are the set of people with pre-existing undiagnosed problems.

I got treatment for it.

It means you've had an underlying issue. It probably wasn't entirely caused by the work-related stress.

After it happens, you know somethin's up, or could be up at any unpredictable time. My goal in therapy and with medication is to manage the episodes while being as much of myself as I can without a relapse.

To your point, I think psychological disorders are common in tech fields. PTSD or BPD, for example, frequently have "control compulsion" issues. Being compelled to control works very well if you are managing a fleet of 10,000 servers. It's been difficult to explain to my old friends why I would care about things like latency and GC STW events because a normal person without control issues doesn't find it emotionally appealing. Psychotic/hallucinatory/delusional features have short-term value in certain situations, like coming up with new product ideas or rapidly "pivoting" between market fits. I won't say it's normal, but I will say it's predictable.

Hiring cycles are more like a clearinghouse than a company choosing the best candidate for a position.

N number of candidates enter that month's job market, companies are able to offer N number of positions.

At the end of the hiring cycle, they make the N-to-N matches and execute the cycle.

A candidate can (and must) have several offers from different companies, just as companies have several candidates for each position.

The #1 reason to split your serving architecture into microservices is that your application can't fit in 1 server's memory.

If your application fits in 1 server, you have a choice, otherwise you don't.

If your application can't fit in 1 server and you can't split it up, you have to refactor so it can.

If you can't refactor your application to have isolated domains, aka your domain is so complex it must take up an entire server, you have a serious problem.

Clustered applications are unavoidable.

Someone who is a flat-earther is probably also someone who isn't concerned about getting a 100% A+ on their homework and tests.

The kids who question the system of schooling are the ones who are doing it appropriately. We don't need to make a 100% A+ incorporate questioning indoctrination, we need to make people not so concerned about getting 100% A+.

In the UK, 80%+ comprehension is considered an A.

Reasons we test for data structures and algorithms:

- The work sucks because existing employees don't know DSA's

- We want people to re-implement and refactor with better DSA's

- We want to know the candidate studied for the interview (took it seriously)

- We actually do want them to know DSA's when joining the team

- It's the least you can do when applying for a CS job

Most recruiters provide links and resources, the material isn't a mystery.

from 2 years ago https://www.youtube.com/watch?v=BpNP9b3aIfY

TEMPEST is available now, for free, on github.

All you need is a $20 RTL-SDR.

https://www.youtube.com/watch?v=QjqpKtGNbQo

https://github.com/martinmarinov/TempestSDR