296 karma · joined November 23, 2015
You might be a strong, mighty genius, but if your ass is "chilling" on the couch 24/7, your exact worth is 0(ZERO)$
Facebook is the circus (as in panem et curcenses) that masses learned to crave
EDIT: same goes for twitter.
CONTEXTUAL EDIT: I understand that emotional weakness, unawareness, and gullibility of the general population is a controversial topic, it is still very useful to be aware of and hence put reminders in place.
> Chrome: No. (it sends every domain you visit to google)
Silly website. There's nothing new or newsworthy. Why is it on HN? Looks like placeholder for the future project
EDIT: also how many times in your career you had a problem where you had to make a significant and time consuming effort over that one line of code (other than hackathons, of course). With practically all high-level langs in modern collaborative environments readability is prioritized. “I should be able to read your code as a well written prose” - uncle Bob’s statement, is pretty much universal doctrine. Ability to type fast here is greatly underestimated
I wouldn't say that it's excellent now. It still has a long way to go. Small example, try enabling captions in Google's meet. Those are awful. Don't get a lot of words right, if you have an accent it's even worse. And distinguishing between different people talking? Forget about it...
imagine writing code as fast as your thoughts are?
Well, also a note: programming is not typing. it's 90% thinking. But at the end of the thought process, it just burns to turn your thoughts into working code ASAP! It would be so nice to streamline, optimize the process of the thought to code transfer. Until mind readers are invented, steno is a great solution
Interesting point. That’s the ideal world situation which encourages self-improvement, self-development. A “natural selection” of sorts. Unfortunately in real world, management that’s smart about resource management and allocation is rare. Very often you can see waste where high-paying devs with valuable skills being tasked to do work that can be outsourced for pennies, or work that can be easily done by a cheap bootcamp graduate. (there are exceptions of course, e.g with dev resource hoarding in big tech)
> suspect you're less concerned about your work environment than salaries being pulled down
Actually I was more concerned about my work environment. With development it's really hard to get a salary that is not directly proportionate to what your skills are worth.
And besides that point above, it took me literally one click to get to the full article. How awesome is that? Right? And if you like the content, subscribe and stop freeloading.
We all demand high quality journalism while not willing to make a contribution. Insane.
Same analogy as with software pirating (ah praise Erik Meijer for speaking up about this stupidity)
e.g every time someone yells "think about the [insert adjective here] children!" it's most likely a clear attempt to emotionally manipulate you, trick you into doing whatever the manipulator wants you to. Very few are capable to recognize and withstand emotional manipulation.
I also suspect that we're going to agree to disagree here. There are so many nuances, it's impossible to properly communicate most of those without writing a chapter of a book.
Appreciate your points though. Great food for thought right there.
If I need to do a roll back it means that I don't trust the system nor the code base. I will do the roll back but after that there will be a very productive retro about how we can do better to avoid rollbacks in the future (aka what did we learn).
But again, as I said, there is a place and time for everything! And there are many variables! Even how you structure your teams affects deployments, engineering culture, engineering team types (cross-functional, generalized; specialized etc), if the team that makes a decision about the roll back is not the team that introduced the bug.
My approach is not dogmatic (have your standardized roll backs if those work best for your company, release cycles, teams) it's idealistic (that's what I aim for, personally)
But again, I also saw the other comment about how "Dogmatic" my approach is. I wouldn't say it's dogmatic, idealistic - yes. But not dogmatic. There is a place and time for anything and roll back can STILL be useful when you don't trust the system nor the code base (as I pointed in my other comment, rollbacks are useful with legacy systems and systems that you have to maintain that were build by outsourced teams).
Well also roll backs is the first thing you think of when you join a large company as a director of engineering to support systems you never touched before.
Also note, that roll back was a valid strategy back in the day and still can be useful tool in your garage of tools. It can be useful when, for example, dealing with complex legacy systems that were created decades ago, or complex systems developed by outsourced development teams. You'll know when roll back is useful when you see it.
Also worth to note, priority bug fix is not really about pipelines it's more about the ability to dynamically reallocate resources. Depending on the complexity of the affected area we should be able allocate as many devs as it is useful to fixing it. (similar to "Fast Lane" in Kanban)
Now we should only march forward with small, on demand releases, this way we will know exactly where the issue is and will be able to fix it forward quickly.
Rollbacks were a strategy with monthly (or even quarterly [insane huh?]), giant, stinky, release dumps, knowing there is no way we could quickly identify and deploy the fix. aka lets throw production 3 months back and take another 2 month for figuring out there the issue that happened during last release is.
And to finally answer your question: we never roll back. We always march forward.
> Go for a walk
It's almost winter in US. Pardon me, but taking a walk in the dark, alone, with your camera doesn't really sound as a good advice.
I bet with your new iPhone you can take gorgeous photos at night but that can be fun only once on the blue moon, not every day?..
You didn't answer the question. If you can't control your basic instinct it doesn't mean that general population reduction will be a "bad" thing.
Population control doesn't mean anything "inhumane" at all. As one above said, countries with higher levels of education have better control over population growth naturally. That's one of the solutions to explosive overpopulation: EDUCATION!
Overpopulation is a real problem. For the environment, for the climate, and for the future.
It's kinds interesting and even exciting to "shop" for new investment opportunities when dividends are posted.
agree about the market and all time highs and it feels dangerous. The thing is that no one can really predict what will happen, the only decent advice is, again, to diversify? Diversify with assets outside of the regular market fluctuations, e.g with cash savings, real estate, precious metals
I also did some passive index fund investments but I only count cash dividends as actual "income".
Disappointing article. I don't need this negativity in my life.