On the internet, they are everyone, and they are no one.
On the internet, they are everyone, and they are no one.
Not if you’re considering security gained versus difficulty of remembering.
character N gives you information about the character at position N+1
There is no point in a password cracking attempt during which the attacker knows the character at N but not the character at N+1
I used to be a kitchen designer. This looks cozy and functional. Would love to have this kitchen.
Long term, the spot above your window could have a floating shelf added for knick knacks or small appliances or something.
Concrete in a super soaker 50
Bitches love ethical abstraction
This is called “running a train on her”
I mean what else are ducts for?
Is it possible the 1500 cfm fans are intended to be run at lower capacity, and are just sized for a factor of safety?
Developer cognition is the most expensive resource on any programming project. It is entirely rational to stick to tried and true ways of doing things. A developer’s mind is generally at capacity, and putting some of that capacity into learning new tricks comes at the cost of all the other things that developer can be doing.
And it’s not just a matter of time. Generally speaking, a developer can only do so much mental processing between sleep cycles.
That’s not to say it’s always bad to learn new things. In fact one has to in order to keep the system working in a changing world.
But throwing shade at developers who hesitate to learn new things is foolish. I’d recommend every developer do shamatha and vipassana meditation so that they can more accurately monitor the state of their own mental resources. Those mental resources are the most valuable and most expensive resources on the project.
You can shut down any computer in ten seconds by holding the power button.
People don’t like it because it’s declarative. It felt cool to be able to just put bash files into certain directories to have them executed on startup. That was elegant, in the sense of “everything’s a file”.
systemd is more of an api than a framework, so it’s a different design paradigm.
I hated systemd until I printed out the docs, for some coffee, and sat in a comfy chair to read them front to back. Then I loved it.
Mostly I hated it because I didn’t know how to do things with it.
Also, “journalctl” is kind of an ugly command. But really, who gives a fuck. It’s a well-designed system.
And if a person absolutely must execute their own arbitrary code they can just declare a command to execute their script file as the startup operation on a unit.
A friend of mine got his to grow with an elaborate system of rubber bands.
IDSPISPOPD
no limits
I use capslock for ctrl
I once deployed a small service in 2016. It was a sort of configurable API, that other companies could post information to. Every company’s information came in a different json structure, but I built the thing to be able to accept a new structure, with new configuration data (no new coding needed for new formats).
Then in 2019, I was interviewing for a job and they asked me to talk about something I’d built that was reliable and I was able to report that this little service, running in docker compose, had been up continually for the last two years with zero errors.
There’s rot
git