All the good content will be gone within 24 hours. Effin gone.
151 karma · joined March 7, 2014
All the good content will be gone within 24 hours. Effin gone.
Sometimes our society recognizes a problem. It becomes a sensitive, emotional topic. Racism, sexism, all real problems.
And when a society is in this sensitive state, some formerly (or even currently) oppressed people take advantage. The oppressors become the oppressed and the oppressed become the oppressors. It's a real thing, and it's quite natural, if undesired.
You don't know what the situation is here. I don't. No one commenting from aside knows.
I've come to a similar conclusion that using @media incantations only covers the basic cases, so any advanced web layout would need a mix of CSS and JS anyway (so we might as well have a solid JS toolkit help us keep things flexible and tidy).
This caught my eye, though: "In one day, all of the work I've done at that company to be a better place for women to work has come undone."
"All work undone in a day" feels off. Either too impulsive, or speaking ill of her alleged work.
I'd be suspicious of anyone claiming great progress in their activist agenda (or whatever agenda) for two years, and then suddenly announcing it was all undone by a single remark or in a single day.
I like Node.JS a lot, as you say it's a tool in my toolbox. But due to the it's nature the code is quite fragile. It's best to keep Node.JS apps small and simple and play to Node's strengths, which are a high volume of computationally simple (and potentially long-running) requests.
That article is definitely hype-inspired.
Your problem isn't battery life. Your problem is you spend many, many hours a day staring at that phone and depleting its quite reasonable battery life. What the hell are you doing that takes you all so much time?
And what's with "last many days". I mean, don't you sleep? Where you sleep, is electricity not available? Honestly, I want to know.
I don't think you're "some kind of direct-current junkie", I think you're a smartphone junkie.
Oh, no we have another Flappy Story in the making here!
As the name suggest, it's just as important to strongly praise to correct moves as it is important to strongly scorn the bad moves.
We don't have emotions as some quirk of our evolutionary paths. Emotions are a tool. Like any tool, when used correctly, it produces amazing results.
"A good traveler has no fixed plans, and is not intent on arriving."
I'm optimizing and seeing what happens. If I hit a stubborn limit, and nothing works to break it, I'll accept it. But at least I'll know what's going on, and as you say, I may plan better the rest of my day.
I found out that during a "8-10 hours workday" I'm actually working, as in coding, getting shit done - maybe for about 2, tops 3 hours...
That's not just an interesting observation, I was FUCKING HORRIFIED. I'm pissing my limited lifetime away!
The first step is awareness. Always. Then comes improvement. I kept tracking myself, now being very aware of what interrupts my work, and limiting my distractions. I have yet to claim 8-10 hours of solid work in a day, but it's getting better.
What happened to all those people proud of PHP's principles? "Shared nothing", remember? Why on earth would your tests share resources and state? This is not Java. It's PHP.
Look at PHP's own tests: PHPT files. They're simple files containing code to setup a test, and the result of a test.
How tests run, well, in a nutshell:
foreach (glob('/tests/*' as $test)) exec('php ' . $test);
Then you check the logs. You can have your little pretty log formatted if you want, but it's not that important:
- If there's stuff in the log, your test failed, you go check why.
- If there's no stuff in the log, you're good to go.
It can catch output, exceptions, even fatal errors. Can PHPUnit catch fatal errors? You need to use its "process isolation features", which is just reinventing the wheel by doing... what I just did in that one-liner above. Well I did it! Process isolation! And I didn't need PHPUnit to do it.
A lot of those "modern PHP" libraries are basically a masochistic exercise in copying designs that make sense in Java into PHP where they make no sense.
PHPT style tests wouldn't make sense in Java. And Java style Unit test frameworks make no sense in PHP.
However all those blindly supporting this, can please continue to waste their time, for the benefit of making sure they're buzzword compliant & in sync with groupthink.
"I write my mocks and fixtures in PHPUnit. Oh yeah it has all the latest assertions, like you can assert XML using CSS selectors". I can almost hear the collective taps on my back just saying this out loud.
assert($condition);
It's useless.