I came across this one just yesterday and while it was convenient at first, I immediately got frustrated when I went to add some parameters and discovered it wasn’t actually curl
I came across this one just yesterday and while it was convenient at first, I immediately got frustrated when I went to add some parameters and discovered it wasn’t actually curl
It’s not just because of nonsense, it’s more that it doesn’t really matter what you do - the only thing stopping someone with physical access to your machine is their level of determination.
At some point, there’s no stopping the laws of physics. Your data is physically stored there. You can do a lot to make it really difficult to access it, but the best you can do is full disk encryption with a sufficiently strong key, and only store that key on external hardware that isn’t accessible to the attacker.
Even then, you better make sure that your encryption key wasn’t hanging around cached anywhere in memory before you shut down your computer.
I like to draw my pages out on graph paper, then just use position: absolute
and tons of media queries to place everything with x and y coordinates. It’s the ultimate grid system.
I would absolutely consider shipping non-minified bootstrap doing something wrong
Grid is just flexbox but worse
TypeScript is essentially the “measure twice, cut once” approach to JavaScript.
Yeah, anything can be anything in JS and the type declarations don’t make it into the compiled JS, but allowing anything to be anything starts to become fairly dangerous when the size of your projects starts to grow and especially when you’re working with a team.
Rather than writing functions and just hoping they always get called with a parameter that has the properties you expect to use, TypeScript helps you make sure that you always are calling that function with the right object in the arguments. You don’t need to debug some runtime error up and down 8 frames in the call stack because this week you named a property “maxValue” but last week you used “maxVal” or you forgot to parseInt some string because you thought it would be coerced - you just need to make sure your types match and eliminate that type of debugging altogether.
All in all, TS really just enforces a bit of sanity to the foot gun that is vanilla JS.
“Dependency injection” is just a term for providing a function or method with its dependencies rather than making the function go and gather them itself.
It’s (typically) done through parameters, but it’s still more specific than just invoking a function. It describes how that function was written and the reasoning for certain parameters. To the other commenter’s point, you’ll have a hard time communicating about your code with other developers if you refuse to use the term dependency injection just because you don’t like OOP.
The US can barely even put sidewalks where it’s convenient. I have very little hope for our local governments to add bike lanes to it.