> Should I be familiar with every step of Dijkstra’s search algorithm and remember the pseudocode at all times?
Somehow, I think you already know the answer to that is "no".
I've been working as a software engineer for over 8 years, with no computer science education. I don't know what Dijkstra's search algorithm is, let alone have memorised the pseudocode. I flicked through a book of data structures and algorithms once, but that was after I got my first software job. Unless you're only aiming for Google etc, you don't really need any of this.
You should know the trade-offs of different algorithms, though. Many libraries let you choose the implementation for a spcific problem. For instance tree vs. hash map where you trade memory for speed.
Antibiotics don’t stop you suffering from poison ivy. At all. In other posts you say you had a broken skin barrier that’s vulnerable to infection, so you presumably know that this is not the same as actually having a bacterial infection, and that antibiotics are only a prophylactic, not a treatment. So stop making out that people are dying to deny you treatment.
But you are going to imply it by bringing it up at all.
> They didn't kill him, they failed to save him.
The post does not say otherwise.
Please give this, of all topics, the respect it deserves, respond to the article as it is actually written, and don't use this, of all things, as an opportunity to get on your high horse about some other article you have problems with.
Me. I'm a backend developer who occasionally wants to make a web frontend for a side-project but knows essentially no CSS. The solutions are not "well understood" by me because I know no CSS.
In that case I'd say the problem is exactly what you state
> knows essentially no CSS
The solution is quite obvious then too: learn some. It's not hard. Understanding the basics is a afternoon job. Diving a bit deeper a day, and learning about some often-used more in depth features like "responsive" or flexbox, another day. For a software developer/engineer that builds backends, CSS really isn't that hard.
That's not to say a basic CSS set and some explanation like in TLA, isn't useful.
It's my pet-peeve that in software development, I'm convinced we should understand the stuff that we work with. Not all, and certainly not everything in great detail, but enough to know where to find the info and details when working with it. From sysadmin to the concepts of cryptography and from accessibility to how an OS writes stuff to disk. Even if that means constantly learning.
> The solution is quite obvious then too: learn some.
That’s the whole point of this article. CSS is a huge language. Where do you even begin? This article is a perfect response to that very natural question.
It really isn't a huge language. It's not even a language. There are some basic principles, but it's pretty much a bunch of pick-and-choose attributes for HTML that you can wrap up into "classes". I've worked heavily with it for 25 years and I still basically just screw around until something looks good.
There is no point to this article. This is the most common kind of trash you can find if you type in "minimum css"... it's not even that. Come on. Have integrity in your work and learn how to do it.
It's a declarative language, not an imperative/functional language. You describe the desired end result, the browser figures out how to lay things out to fit all the constraints.
And this:
> but it's pretty much a bunch of pick-and-choose attributes for HTML that you can wrap up into "classes".
indicates despite using it for 25 years, you haven't even tried to learn it. This may have been partially true back when it was first introduced and all people knew were things like "font" and "[text-]align", but it's been a horribly inaccurate description of CSS for decades now.
C'mon. I'm a full stack dev but this is like me saying I just want to code something quick in C++ but don't know anything about it. Maybe I don't know how to tell a pointer from a shared_ptr or what a destructor is. Even if I don't know how to do them, I'm pretty aware that these things are very well understood and documented by a huge community, to the point that I probably wouldn't rely on some AI-written article with almost no useful information to show me how to do what I wanted to do... I'd want to actually learn what was going on under the hood... and if I did somehow find such an article useful to explaining pointers in the most vapid way possible for my use case, I certainly wouldn't post it to HN. And if I did post it to HN and it suddenly ranked to the top, I would think something had gone completely wrong with the universe.
It's an objectively terrible article. It gives a bunch of arbitrary things to copy without really explaining them, and it is completely useless for building anything real. It is probably written by an AI. It's trash. What on earth makes you think it deserves more attention than the other million useless articles on this subject?
The article, and especially much of the discussion here, is about how privatisation has led to this situation. Privatisation of a public utility which _even in many other developed liberal capitalist countries_ is not privatised. Yet to you this is not evidence that we are an extreme example of neoliberalism, but somehow “defacto socialist” and your solution is throwing fuel on the fire with more privatisation. You’re living on a different planet, mate.
Fruiter Aero is a term that retroactively applies to the style of a certain time. Look at Windows Vista. Windows Vista's design is what we now call Fruitger Aero. Windows Vista came out in 2007. It's a retroactive term, yes, but how can you claim the thing it refers to didn't exist before 2007, when Windows Vista is a shining example of it?
I'm not sure how you've come to that impression. The boards I used to frequent are hobbyist ones, not political, yet they have people calling each other the n-word all the time. On /fit/ anything done by a large corporation or as a moneymaking scheme is talked about as if it's a Jewish conspiracy, to the point where they call highly-processed food "goyslop". /g/ hates Indians and calls software and technology that it likes "the white man's choice." I could go on. This pervasive background of racism is all over 4chan, and I wonder why you're trying to downplay it.
> Why not pick a good option? Why go through the trouble then be like, fuck it, Ill pick a shitty option?
You're assuming way too much active thought and choice on the part of the people who don't care about cookies. You're assuming that it was a choice between options at all.
In my case, a website I was happening to read mentioned the I Don't Care About Cookies extension, and I thought, "oh, it'd be nice to have something that stops all of those annoying cookie pop-ups" and installed it. That is all. Is such an action really an "anti-progressive and pro-shitty attitude"? Am I really harming you or myself or society by doing that?
