“Self-documenting” just means “(I thought) I understood it when I wrote it, so you should too”. In other words, it really means “I don’t want to document my code”
jvisick
I would absolutely consider shipping non-minified bootstrap doing something wrong
Grid is just flexbox but worse
My favorite approach I’ve seen is just units of time -“this task will take a few [days/weeks/months/years]”.
No specific number. Instead, the scale of the task is measured in one of those units and I can give you an estimate but it’s just a guess.
If it’s task that might take “a few days”, it could be done tomorrow or it could take 5 days. If it’s one that takes “a few weeks”, it might be done next week or maybe next month.
What are they going to do if they don’t pay? Evict them?
What bike do you use and would you recommend it? I’ve been looking for an e-bike recently since I work so close to home, but I haven’t found any that seem reputable and a good value. I’m definitely looking for one that’s easily repairable and not paired to a specific brand’s software or proprietary parts.
Granted, I’ve only been passively looking (I.e. when I see an ad or doing a quick google search sometimes), but from what I can tell most of the advertised bikes are just the same handful of models with a different logo slapped on it and dubious claims about its performance.
The Odin Project is an excellent resource. I’d recommend working your way through both the “paths” they have - take both the Ruby and JavaScript paths. To land a job you’ll want a thorough understanding of the back end and while Ruby doesn’t have as high of a demand anymore, I do think it’s important to build skills in more than one language to be a compelling candidate. If you don’t want to take the Ruby course, I’d recommend learning how to build a back end in C#/Java to make yourself more well rounded.
They also recently released a React course - I haven’t checked that out yet, but it’s a highly marketable skill and the rest of their curriculum is great so I’d imagine that is too.
In any case, they do a great job in teaching you how to “think like a developer” instead of just how to follow a tutorial- which should give you a good foundation for building your own portfolio. TOP played a huge role in landing my first job - but you do need to hold yourself accountable to studying every day if you want to succeed through self-studying.
You’ll never understand why people want to check out the latest app from a major tech company?
I get it if you aren’t interested personally, but it seems strange to not understand why people would want to try it.
I only use packages that are from a reputable source and/or have a huge amount of downloads. It’s not a perfect system, but I’ve never had a problem so far.
If the downloads are low and I’ve never heard of the author, either a) I don’t need it and can build a solution myself or b) it’s a niche package that’s small enough that I can audit it by skimming the GitHub repo.
The normal common sense rules still apply - check for typos and any attempts to look like they’re a package or author that they’re not
There’s nothing to stop an admin from hosting a static front end for their Lemmy instance if they’d rather, but it’s clear that SSR is a goal here - and I think the default UI for Lemmy really should include SSR for plenty of reasons. And, if you’re already hosting a Lemmy instance, you definitely already have a host that can support Rust (at the very least, in a container).
It depends what you’re using them for, but it’s pretty common to use the original icons of other services/companies if you’re using them on your website rather than a stylized version.
In my experience, anyways, that’s more common than using a stylized version of a 3rd party logo - and that’s not to mention potential legal issues with using an altered version of a 3rd party’s icon.
By necessity, when you’re in the debugger your code has already been compiled either way, no? Or am I missing something here?
This isn’t executing your code as you’re writing it (though it does support Edit & Continue), this is preemptively executing the next lines in your code when you’re already paused in the debugger - which means it’s been compiled and already running.