1 karma · joined August 17, 2024
I'm afraid you are drastically underestimating how much it actually costs to install fiber.
When I merge changes from someone, the commits are always imperative. If there are two approaches taken, say "Use <method a> to foobar" and "Use <method b> to foobar", then the imperative case makes way more sense.
From my perspective, picking a commit to my preferred method is very wonky when it says, "Used <method a> to foobar".
If you know the kind of functionality you're looking for, this quickly becomes way overkill.
Facebook has constructed a business model on captivating people to spend _as much time as possible_ on their site. Google's search engine does no such thing.
If you're a solo developer, stick to _standards_. There are standards for how something should be implemented (like REST), there are standards to how things should be written (like PEP8 for Python), etc.
Follow those standards as close as you possibly can. Ultimately, you'll find issues with them -- that's great! Perhaps you'll even find a more clear way of doing something that the standard doesn't suggest. This means you can probably iterate on your original design.
Join a Slack/Discord/IRC with other developers using your toolchain and ask questions there if you have concerns. If you're worried about design decisions, find others who have been in similar boats and ask how they did things and what the result was like.
Typically, best practices are those that emphasize 1) clear code, 2) readable code, and 3) the KISS principle. Anything that favors complexity over simplicity _must_ have a good reason for doing so.
No. It used to be like this. Maybe in the mid-2000s when 4chan was first getting popular, it could have been seen as this. It might have been seen like this during the early 2010s, does anyone remember Anonymous and how it started basically from /b/?
It used to be a troll site -- it's not anymore. It's literally a cesspool of white supremacy. Seriously, go read what's on /pol/ right now. It's not shock value, it's sympathy.
We might be able to finally run more safe cryptography in the browser with constant-time guarantees (there are other concerns with browser-based crypto though).
SHA3 and Blake2* use different constructions that don't have these flaws, thus they don't require HMACs for their needs.
Whether your work is representational or non-representational, it's extremely difficult to go from what you have in your head to what you put on the canvas.
If you have a thought, an idea, or even an emotion you should practice putting _that_ on canvas. The technique will come as you paint more and more. YouTube can help for some techniques if you want to figure out how to do something.
Really, just start painting and the rest will come. Experiment with texture, shape, and composition. Don't worry too much about color. When you start getting better at composition the colors become obvious. I'd even recommend your first few paintings just stay with a single color.
Scheduling isn't meant to be some Randian, individualistic practice. It's a collaborative effort between people that should say something of the effect, "My time is valuable, as is yours. You seem to be interested in something I'm doing and I'm interested in telling you about it. Let's find a time that's agreeable to both of us where we are both unencumbered and can freely associate."
If you're not interested in meeting, then you have options: 1) Ghosting (controversial, but some requests deserve this response), or 2) Refusing to meet.
Instead this reads as, "I value my time far more than anyone else I associate with. If I so happen to be available, then I'll reward you with the charity of my time."
One of these is professional and makes other people you associate with feel valued, the other makes you look like an arrogant ass.
Is it just me, or does this come off as exceptionally arrogant? It's literally just telling people to plan their lives around yours. It just seems like time spent with this individual is a token of charitable _grace_. This is the opposite of what I'd expect professional behavior to look like.