An interesting POV. I certainly hope that's true. Is IBM reputation good in the contractor space? As in, are their services largely viewed as dependable and good value?
How does that make sense? Can the "grad" do good enough job compared to a senior? I've seen my fair share of "senior" developers, who had insanely high salaries for some strange reason yet their output was mediocre at best. Laying off these people I can understand.
That said, management is notoriously bad at spotting these people. Chances are they lay off the only person who knows how some crucial piece of SW works...
I love the idea of "Steve" or "Ariana" at Asana thinking "Oh, another email from whiddershins, better write that down for him into his account. Good on you, mr. whiddershins!":))
There is a spectrum of meditation activities. What does and does not constitute 'meditation' depends on one's training. I've heard the arguments of "I don't need to meditate, running is my meditation", which some may agree with to a certain degree (like Dan Harris' 10% Happier book) and others strictly disagree with (like pretty much anyone who's done a week or two-week long retreat).
In the end, the question is, what are you looking for in meditation. If all you're looking for is to slow down a bit and maybe get some benefits along the way, Headspace is fine. If what you're looking for is to transform the way you're experiencing the world (which is very much possible through meditation), Headspace isn't gonna help you much. It might be a good stepping stone, though.
We all have 'flags' that turn us away from a particular source of meditation. For some, it's the music employed in yoga/meditation centers. For others, it's the marketing, as you say. For me, every time someone mentions the 'ancient texts' and its superiority, I cringe a bit. That, to me, is very much the antithesis to meditation--fixating on a single source of truth, possibly long forgotten, that is.
> But who is willing to pay for all the documentation?
Anybody who wishes to be successful. RPI would not be as successful had it not been for the ton of materials on it online, be it by the manufacturer, or the tinkerers. Any newcomers wanting to de-throne RPI must differentiate themselves; good documentation is simply expected at this point.
Well, I personally like it to just satisfy my curiosity about what are some of my friends and coworkers up to. Generally, I am quite curious about what is my friend/coworker/ex-coworker/... doing, and I am genuinely happy when someone I know gets promoted, or gets a new job.
I looked over the Linux questions, and they were pretty bad:
Q.1: What is the core of Linux Operating System?
Shell
Kernel
Command
Script
Terminal
I mean... If they asked me about that at an interview, that'd be a huge red flag. I wouldn't consider this list when studying for interviews... It is sad for me how many stars and forks this list has. Hopefully, it's much better for other languages/topics.
"A startup that really wants people working 80 hours a week" sounds like the most US thing I've heard/read this month.
The US work culture is utterly insane. They say that the Japanese work extreme long hours, but from my experience, it's quite similar for big cities in the US.
Sounds like a sure way to a burnout, getting fat, and losing your family.
The thing is, "somewhere in the backend" is generally accessible from the internet, and vulnerable to attackers (so you need only a maliciously crafted packet, or something similar); whereas for 7-zip vulnerability, there must be: a) a maliciously crafted zip file, b) a user who wilfully opens it.
What's more, getting into one's backend servers/gaining some kind of access to DB, config files of the machine, etc. is, in my mind, just infinitely worse than gaining access to a computer of a person/uploading some ransomware/something similar.
We're just probably working with different SW, so we both see the thing that touches us the most as the problem... :))
Sure, but there's a difference between "yea, we like 7-zip, let's put some money into it" and "yea, we use Tomcat to actually run our apps connected to the DB, might be nice if it got a bit of patching" (and funnily enough, some of the user-centric apps have more funding than some of the backend, mission-critical SW).
This is a very strange distribution of projects. There are projects like VLC, Filezilla, and 7-zip, next to often mission-critical pieces of software, like Kafka, Tomcat, and GlibC. I wonder what went into the decision process to include each of these libraries.
I also dislike the 'bug bounty platforms'. Why can't I simply report it upstream, and if accepted, claim my price? Each of the projects should have CVE protocols and procedures. The idea probably is to curb the zero-day vulnerability leaks, but I assume that if you're able to find a CVE, you're capable of finding a CVE procedure.
Because all of those who started on something like C, C++, or Java have way better programming practices? My experience tells me that starting language is literally not a vector in determining how good of a programmer someone is.
I upgraded from MBP 2012 to the 15" 2015 version the last year. I'm sure 2k15 will be fine for a while, but this is unsustainable with the direction Apple computers are going. It's more expensive than ever; in Europe, I paid 2300 USD for the baseline 2k15 15" MBP; that's just crazy to me, and the baseline newest 15" MBP model goes for 3000 USD.
Also, their anti-consumer practices, such as simply selling keyboards they know will break (and that are also bad! I thought the 2k15 keyboard was already bad compared to the 2k12 non-retina MBP), and not repairing anything in their MBP (check Louis Rossmann's Apple videos), are just a signal for me that the MBPs are not for power users.
At work, I use the X1 Carbon 6th gen with Linux on it, and though I really like OSX, the hardware is starting to be nothing but farce. For that, I think I'll happily buy some Lenovo/Dell as my next personal laptop, and simply fiddle with Linux.
2/3 of the price of a MBP for the same HW at the cost of spending a bit more time with the OS is acceptable to me, personally.
For enterprise software, a couple days is indeed strange. For OSS, it's standard in good communities I'd say. When I filed bug fixes against Tomcat, I often had fix within that day (though it was released only during the typical release schedule of Tomcat)