This blog post is the second in a series of posts I’ll be attempting to make every week to help me reflect on the things I’ve read this week. You can check out the read this week tag for more entries in the future.
I track my reading habits using reading.am and occasionally, I work on providing a week review of the things I’ve read here with a short blurb. This is my way of writing a really short book report but not for books and definitely not a report. Check out my previous (also first) entry!
Some Initial Thoughts by Josh Marshall
I didn’t follow too closely to the debates (I rarely do); I tend to read recaps
and not spend time watching, in real time, people not giving a shit about my
existence but yet still want me to contribute to theirs.
</rant>. This however:
Even if Trump collapses over the next few weeks, when we look back on this race, I think it will be clear that in various ways over several weeks, Donald Trump destroyed Bush’s candidacy.
That is something I’ve noticed from reviewing the points slung from either party. Something else we already knew:
On balance, not a dominating night for Trump. But I think he maintained a hold on the issue that is driving his success: xenophobia and extreme hostility to immigrants.
Can Trump even do that?
Google Is 2 Billion Lines of Code—And It’s All in One Place by Wired
She (Rachel Potvin) estimates that the software needed to run all of Google’s Internet services—from Google Search to Gmail to Google Maps— spans some 2 billion lines of code. By comparison, Microsoft’s Windows operating system—one of the most complex software tools ever built for a single computer, a project under development since the 1980s —is likely in the realm of 50 million lines.
So, building Google is roughly the equivalent of building the Windows operating system 40 times over.
Bruh. In short:
To be honest, this is an interesting view point with the whole explosion of micro-services nowadays. I figure that people would store the logic in separate trees but it seems like it’s going to be a central tree that handles everything but can be used to invoke specific parts when necessary. The latter is the approach I’m taking for a personal project.
Your First Job May Not Be Your Dream Job by Treehouse
Entry level positions, with limited experience, may not be where you’re expecting them to be. They’re not in the companies with the aforementioned generous perks.
Yeah, we need to un-plug from the over hype of Silicon Valley, man.
It’s not the end of the world.
I need this to be told to me after every interview. You put all of your faith, effort and hopes into this interview only to get a ‘no’. It’s beyond disheartening.
You’re not expected to work there all your life, a year under your belt is enough experience for other employers. It’s perfectly acceptable to move on after a year.
This little difference in software companies from traditional companies is something that’s hard to translate to people in other fields or transitioning in. “I don’t have to stay? Why did I join?” I’d say to learn and grow.
I didn’t read any physical books this week ! It has been solely an web article and podcast heavy week. I’m going to have to skip some episodes of upcoming ones and stick my head back into books from last week.
That’s it for this week. I take suggestions for things to read very openly via email or Twitter. Let’s see if I can keep this up !