There’s a lot of factors. Depends how well your content lends itself to being cached by a CDN, the tech you (or your predecessors) chose to build it with, and how many unique pages you have. Even with pretty aggressive caching, having a couple million pages indexed adds up real fast. Especially if you weren’t fortunate enough to inherit a project using a framework that makes server side rendering easy.
I think they make good devs 2x more productive for the first month, which then slowly declines as that good dev spends less time actually writing and understanding and debugging code until it falls well below the 1x mark. It’s basically a high interest loan people take against their own skills. For some people that loan might be worth it. Maybe they’re trying to change their role in an organization and need the boost to start taking up new responsibilities they want to own. I think it’s temporary though. The slow shift into “skim mode”, where the authors just don’t quite put that same amount of effort into understanding what’s being churned out. I dunno, that’s just what I’ve seen.
This is so simple and makes so much sense. I’ve seen a couple libraries that do something similar, but I feel like this is obvious and useful enough that it should just be a stock pattern, and it clearly isn’t.
I got one of these from the latest batch last week and I’m not entirely convinced by it yet. I need to experiment some more but I went back and did a couple rolls from this summer and so far I think the cslite warm setting + negative lab pro results are better and more consistent. I’m still getting some wonky colour casts with it. It’s nice that the control app lets you change the power of each LED colour separately, so that’s the next thing I’m going to experiment with.
I’ll also note that negative lab pro hates negatives that are scanned with it. They don’t turn out at all. If you’re using it, you should expect to be inverting them manually, which is kind of a pain. I was quietly hoping (but not expecting) to still see some of the benefits of it when passing them through NLP.
All the current Nikon Z bodies (and probably other brands too) have different levels of pixel shift where it’ll take 4 or 8 images and basically cancel out that it’s a bayer sensor. The bayer array is a 4 pixel pattern, so it moves one pixel to the right then one down and then one back to capture all 3 channels for each individual pixel. For things like film scanning it works flawlessly, I use it all the time.
Then it’ll do a 16 or 32 shot stack in order to do the same thing but with more resolution.
The router is really baffling, agreed. Magic file names make me so frustrated, and even more so when they all start with the same prefix so all my editor tabs look the same. I wish they’d just make a simple single file router that works the same as every other one. There are a lot of things that aren’t perfect in Vue, which I primarily work on, but the router isn’t one of the things that bothers me. It mostly just works.
I’ve seen this one a few times and something about it doesn’t agree with my eye. It’s somehow in the weird awkward zone of not old enough to truly feel simple and functional, but not new enough to look modern minimal/clean. Might just be the font also, but I don’t find it very easy to read. Could just be me though.
You certainly can, I specifically like being able to see it in real time though. It’s less useful if it isn’t constantly present without having to bring it up with a click/command.
Maybe I'm just a scrub, but something that I find makes it harder to do smaller commits is that I frequently rely on being able to see which lines I've changed directly inline in my editor. When you commit, vscode now stops highlighting all of those lines, and that makes it much more difficult for me to orient myself relative to what I've already done. The individual lines, and the git pane that shows which files have been changed, act as waypoints for me while I'm working on stuff. It's particularly important on more complicated features that span more files, and I'll often intentionally commit stuff I feel like I'm not likely to touch again to reduce some visual noise.
I think everyone is wired a little differently. I agree that sadness isn’t the right word for it either, apathy and empathy and hopelessness are bang on. But for me, I guess I take refuge in learning. I find it hard to go and do anything physical or social, and the only outlet left is to learn obsessively cause otherwise I’ll lose my mind. Maybe trying to stockpile knowledge for the day when the hopelessness goes away and it’ll end up being useful?
Elixir is spectacular for visualizing, it’s all just changing the shape of your data all the way down, and all the standard modules have exactly the right tools for doing whatever step needs to come next. It’s so easy to find yourself zoned in. Go has the rhythm of error handling everything, it feels like you’re steadily plodding along with these mini checkpoints.
Discord is just absolutely worthless for this. Any question that gets asked gets buried in days if not hours. It pretty much guarantees the same basic garbage gets repeated over and over and over forever. Basically the exact opposite of stack overflow.
That’s super interesting. What was the ideal ratio, back then. Is it still the same now? Or I guess maybe it depends on the specific role and could be different in each. What exactly do you find valuable about thinking in these terms?
Are you still going to have the skills to review it a year from now? Or 5 years from now when you’ve become accustomed to only writing <20% of the code? I’m already witnessing my coworkers skills degrading because of this, and it’s only going to get worse. Programming is a language, and when you don’t use it, it fades.
RawTherapee is great in most ways, except that all of the curves for adjusting anything have absolutely catastrophically bad handling. It's so amazing having access to the Lab colour adjustments but the sliders are abysmal, impossible to make any kind of precise adjustments, impossible to reset an individual slider/point back to it's default placement, impossible to undo the last action without resetting the entire widget to its default state. It's unusable, and I'm convinced that the popularity of it would skyrocket if they'd finally just sit down and address that it's miserable to use. I would drop lightroom in a heartbeat if they made them even a little bit better.
I know it's a different space, but as a counterexample, FabFilter makes audio plugins that are the gold standard for that kind of interface and it isn't even close. Anybody making an interface for interacting with points on a curve should sit down with the free demo of FabFilters Pro-Q3 for just a few minutes to experience what's actually possible and how it should feel.
To me, it seems like it's because the thing you're fixing is actually the "runbook" that's being run. Instead of separating the documentation from the code, they're married together so it's easier to keep them in sync because you aren't having to remind yourself to go edit this secondary location when you make a quick change.
I'm cautiously curious about something like this, although I haven't tried it personally.
Anybody else just see this? I noticed I had it out of nowhere, had no idea what it was. It had a one star rating and apparently everyone else had the same experience. Anybody know what happened there?
Just to further hammer point 2 and how it’s a problem in the real world, Express, probably the go to server library for close to a decade, has only within the last couple months sorted out not completely swallowing any error that happens in async middleware by default. And only because some new people came in to finally fix it! It’s absolutely insane how long that took and how easy it was to get stung by that issue.
The left eye/right eye option has been around even on lower end cameras for the better part of a decade, which is kinda wild. My fuji from 2017 has that, and Fuji are specifically known for having worse autofocus performance than Canon or Sony or Nikon. Nikon and Sony specifically seem to be top of the pile right now.
The Z8 has a whole separate processor dedicated to autofocus and the viewfinder which, in practice, means it can shoot 20 FPS full quality 45 megapixel RAW files with continuous 120fps autofocus without blacking out the viewfinder for each shot, which is absolutely insane.
There's a really specific behaviour that iOS has with its collapsible top bars that I've been trying off and on to nail with CSS for ages as a little puzzle, but for some reason it's always not quite right. As you scroll down or up, the bar remains perfectly in place and only starts moving up once it's fully revealed or down once it's fully gone. There should be a way to do it with `position: sticky` but whether you use some javascript or not, it's always slightly jerky or wrong, especially on safari. Apple really does pay attention to these little things in ways others don't.
And then they go and release that recent photos app update and make me seriously want to leave their ecosystem completely.
What did you use it for, specifically? A personal project, or did you work on something that already used it heavily? I’ve played with it, and it’s interesting, but I haven’t quite found a reason to use it yet.