I'm not sure how you can say hierarchical organizations that use violence/coercion are in any way anarchist. Anarcho-capitalism requires voluntary engagement in a system of contracts and so forth. (Whether that could actually work in the real world is debatable but beside the point.)
I think they suggest that people can be made aware of their incompetence after feedback, but the right kind of feedback often isn't given because of cultural factors that make it unacceptable to give "negative" feedback and also hard for people to accept "negative" feedback.
That idea seems positive to me. If we could change our feedback mechanisms (via education and so forth), we could increase self-awareness and reduce incompetence.
Also, we tend to think of "incompetence" as extremely negative, but they use it in a specific way that is meant to be descriptive and not an insult.
Anecdotal, but PostGIS is the reason I started using Postgres several years ago in some of my own projects, which later came in handy at different jobs. At one place, we standardized on Postgres partly because of PostGIS.
I think Django has had some influence too, since they've always recommended Postgres.
Building your own is educational and maybe even fun (to a point), but it's not going to magically fix these kinds of issues. Most if not all frameworks support navigation and custom framework XYZ probably isn't going to do a better job.
The fact that some sites do a bad job at navigation, performance, or whatever really seems orthogonal to me. We can also come up with numerous examples of "classic" sites that are slow, bloated, and have a bad UX.
I think the argument is something along the lines of: the public hears that an engineer is making certain claims and then push for the laws to be changed. Running of yellow/red lights ends up killing a lot of people. Perhaps without this passive enforcement, more people would die.
Having read some local news about the incident, it sounds like his wife blatantly ran a light according to the laws of Oregon and he attempted to get it thrown out using a dubious technical argument.
This perfectly articulates something I tried to get across to upper management last time we hired a manager for our team. It seems so obvious and reasonable, but they wouldn't hear it. So, we ended up hiring someone who not only had no real management experience but who also didn't particularly _want_ to be a manager, instead preferring to write code.
This created conflict exactly as you'd expect and team morale fell apart, projects slipped, etc. Of course, management takes no responsibility for this, instead diffusing blame to employees via suck-it-up type platitudes (couched in "nicer" language but with that essential meaning).
> selecting CSS colors in other colorspace (eg. RGBA) as oppose to just hex
I'm not sure if this is what you mean, but you can go into the dev tools config and change the default color unit under Inspector. The eyedropper will show values using the selected unit and style rules will be converted to that unit.
Go is still a pile of abstractions built on top of another pile of abstractions that almost no one fully groks. It doesn't seem significantly less "magical" than any other commonly-used language, especially from the perspective of non-wizards, even if it might be a better tool for casting certain spells.
I thought `createClass` does/did something essentially similar to what `class` does in ES6. Not having to use a framework's custom class-creation machinery doesn't seem like a big loss to me or like it is has anything to do with functional programming.
I just tested some things in PyCharm. It has no problem with word_word or wordWord as variable names. It's even smart enough to flag just the non-word in word_ajsjasjasa.
It will also put a squiggly under camelCaseWords in Python code by default, but that's because of PEP8 style rules, not spelling.
It sounds like the sites you've worked on didn't have enough UI complexity to make something like React necessary. Even for a relatively simple admin or dashboard type site, using a more modern framework/library will make it much easier to build and maintain.
It's true that you should think about what you're doing so you can avoid mistakes (and, as a side effect, type less), but you still end up typing quite a bit as a programmer, and you probably want to minimize the impedance mismatch while you're translating your thoughts into code.
I've seen this play out in real life with two programmers who were roughly equal in terms of thinking in abstract terms. One of them was much better at typing (and using tools in general), so their code quality was better overall. The other would get frustrated in the translation/typing stage and produce lots of sloppy and incorrect code.
That sounds nice, but it seems like most if not all work relationships are based on at least dishonesty through omission if not outright lies.
Employers rarely give a full and true picture of what it's like to work somewhere. It's mostly "everything's great" and "all the people are great" and so on. You might get a bland "we need to work on X" if you press them, but they're very unlikely to be direct about the day-to-day drudgery, dysfunction, etc.
Due to the asymmetrical power relationship of employers/employees, I can't see a real ethical problem with lying in response to a question they shouldn't be asking in the first place.
As someone who smokes occasionally, it sounds to me like you're just making excuses. In the past 10 years or so, I don't recall ever having to throw a butt on the ground. There was always an alternative.
Regarding your #4, that sounds nice and all, but that doesn't keep butts from ending up in streams and strewn all throughout the environment.
So often people will throw their butts on the sidewalk or in the street even when there's a cigarette-specific receptacle right nearby. There seems to be a cool factor there with the way people flick their butts away.
My technique is to rub out the burning part above the filter on the bottom of my shoe and then throw the filter in the next bin I see. That's just one idea; I'm sure there are many others.
It looks like the author prefers Django REST Framework (DRF) instead of Tastypie. I can't compare them on their technical merits as I've never used Tastypie, but I do know that DRF is actively developed and has some kind of backing. DRF is one of my "always on" Django packages.
The one problem I have with this is that I want `mail.example.com` to always open in my work container, but `mail.example.com` redirects to `mail.google.com` and the latter is what ends up being saved, so it's not possible to assign to different Gmail accounts to different containers. I wish I could edit the URLs for sites assigned to a given container.