braindouche

>In theory this sounds great but in reality every major application, game, operating system and even website is written in an OOP style. Why is that? People should first answer that question.

Ok, try this on for size: OOP in general has one characteristic that makes it fantastic for large-team development, and that's extending over replacing. OOP makes it easy to never remove or change any existing code, and also "easy" to make changes or fixes by only adding more code. I wouldn't call it a good thing, but it does enable enormous numbers of people to all work on a codebase productively at the same time. I think this, more than anything else, is the power of OOP.

> And if OOP is so horrible why do so many people write OOP style PHP and javascript where they really don't have to?

Numbers. OOP supports big teams, so there are lots of OOP programmers in the wild. I genuinely think Javascript is sucking up to the Java developers of the world, and PHP is genuinely better for adopting OOP bits and pieces, but I'm not entirely sure why OOP devs and Java devs in particular seem to be immune to the industry mantra of "stay current and learn new things".

Nonsense. The water in a hookah cools the smoke, but doesn't really do much filtering, and it DOES NOT remove nicotine. Hookah smoke is fairly low in nicotine, but that's because most shisha is "washed" to remove most of it's nicotine -- kind of like how decaf coffee still has a trace of caffeine in it. Try an unwashed shisha some time, they're out there.

>I sometimes wonder if the problem isn't exactly the opposite of what people think they are. Women are underrepresented in tech because they get more support, not less. More choices, and they get pushed to go for the truly glamorous choices.

There might be something to this. I've anecdotally read somewhere that there are now more women in med school and law school than men. If that's true, and women are over-represented in even higher-echelon pipelines, are they funneling women away from comp sci? It's not the solution, certainly, but the answer to that question might be interesting.

This has also been my experience. Enterprise systems really went all-in on Angular 1 for some reason (I personally suspect because it bridges reactive and MVC), and when it was time to move to a fully-reactive front-end framework, in my opinion Vue and Angular 1 are similar to each other in a way that React is not similar in relation to either of them or Angular 2+.

I still can't quite put my finger on why Angular 1 and Vue rhyme, though. It's common wisdom that "If you know Angular, you'll pick up Vue quickly", and it seems to be true, but nobody has ever explained to me why. Is it the state management? Reliance on viewmodels? How they're more complete systems out of the box and can be reasoned about holistically? Help a girl out, HN.

I'm a programmer and as I told my auto mechanic, my job and his job are incredibly similar most of the time: take the thing, use experience and references to figure out why the thing isn't working, then use tools and resources to make it less broken, and spend a lot of time complaining about the quality of the work done on the thing before you got access to it.

Give it ten years, you'll change your tune.

Tell that to all 50,000 people in my company, and the product owner I'm working for, who are forced to use it by Infrastructure, and 0.0% of our customers.

Yeah, that was me, sorry. I wasn't given a choice.

I mean, yes there's nothing wrong with engineers struggling and pushing their skills and boundaries, it's how we grow and improve. But persistent struggling with daily tasks is indicative of a deeper problem. There might be missing knowledge, or the mistaken idea that programmers should be hard workers to be productive.

Using our tools of simplification, abstraction, automation and domain knowledge, it's critical to teach your juniors how to be optimistically lazy and do less. That's how we raise great engineers. Otherwise, we're just raising mid-level programmers who only know how to throw lots more code at their problem, and as I hope we all know by now, more code never results in fewer problems.

I'll go so far as to say here's my College Drop Out Self Taught In The Rust Belt Salary:

2006-2016: $25k-$45kyr, $40-$120 per hour. The first half I ran a very small agency that maxed out at 4 people and I wrote all the code, the latter half I was a PHP freelancer. Most expensive WordPress consultant in my city!

2016: $52k. Agency web dev. I've never hated a job more. Mostly wrote hacky jQuery and supported an awful laravel app the boss was enamored with.

2017: $65k. Front End Engineer. worked on converting a legacy SaaS product into Angular SPA. My boss begged me to ask for a raise (the recruiter screwed everybody), and then I got laid off two weeks later with like 25 other people. Loved that job, sad to lose it.

2018(current): $87k + bonuses. Senior Front End Developer. My job is to hack .net with javascript. I think the salary trend is moving nicely. I'm suddenly the richest person among all my friends and the third-highest earner in my extended family. (My family isn't even in the rust belt, they're from a much wealthier region in the country.)

"(unless you can manage to turn the road system into a closed system, like rail is)"

I still don't understand why everyone is working so hard trying to make smart cars when it seems like smart roads that control dumb cars would be a simpler, if more expensive, solution. Why not make it a closed system?

That's optimistic. I usually see it at about 4 years, which is absurd, and directly leads to the 26-year-old senior dev I worked under a couple of jobs ago, who's primary concern in code reviews was that I always cache my jQuery selectors "for performance reasons".

As a gay woman engineer, I've always had the policy that, while I'm at work, any part of you that touches me, I get to keep.

What ever happened to that fad where an animal shelter would release a flock of puppies in your office for an afternoon? I'd be into that.

That's reasonable, but at the same time, unless it's a top-secret clearance job, don't threaten me with doing web development on an air-gapped machine. We both know it's absurd, just don't do it.

> if you feel like you will never get a fair cut of wealth in the current fiat economy, well, start a whole new economy where you hold all the tokens.

wait, so crypto is the foundation of the failboy economy? Clean your room and hodl? I... I understand everything now. ascends into the clouds in a blaze of enlightenment

Precisely. As I frequently like to remind those around me (because I'm a total drag), "Coding isn't easy, but it's also not the hard part of programming".

As a woman...

we have a secret: a lot of us also choose to "hide" behind gender-neutral usernames. It's a thing that makes life easier on the internet.

That's a pretty good tax bill for a house assessed at $150,000, which to me suggests that the neighborhood hasn't been reassessed since it was built. I bet that won't last much longer.

> you lose the cascading advantage

while at the same time you maintain the cascading disadvantages. You can't prevent CSS from cascading unless all your styles are inline, or you've OOCSSed your project so thoroughly that you've used classes to recreate inline styles.

Pilot 78g beats Pilot Metro in weight and nib quality, in my opinion, though metros are prettier on the whole. I'm particularly fond of the B and BB variations.

Scoping CSS is great, you can do static analysis, idiot-proof just-in-time stylesheet loading, and when done correctly it eliminates a lot of specificity issues. It doesn't scale well though. Eventually you develop http-call bloat, and unless your CSS is written by a single and very devoted person, consistency becomes nearly impossible to maintain.

Visual consistency begs for DRY CSS, and DRY CSS tends to bend back towards single global stylesheets.

The web is a flexible place. When I started writing code for money, I was working up user-facing PHP interfaces to databases, and I was called a back-end developer. 7 years later, doing fundamentally the same work only moreso, I was called a front-end developer and paid 10k less a year. Everything is always in motion.

I disagree by agreeing, sort of. Geekspace is alienating, but with some notable exceptions I don't believe it's on purpose. I know loads of amazing girl geeks (we are mighty), and my anecdotal observations suggest that there might be a higher geek-to-normy ratio among people of color than there is among whites. And yet, we tend to go play among ourselves, because the white male geeks can get all weird when we try to play with them.

Not always. Not everyone. Just sometimes. Mostly not on purpose, and mostly because they don't have any practice playing with girls or people of color in the geekspace. Enough that it's not always worth doing the work of making the white male geeks be used to having girls and people of color around because we just want to go play our geeky reindeer games.

Then check out Dr Atkins New Diet Revolution, and an older copy at that. Keto diets are roughly equivalent to Atkins' "induction phase", and Atkins followers have known for decades that you can stay on induction (against the advice in the book) for as long as you like. NDR addresses your concerns on processed meats directly and does suggest a wider variety of foods.

Still weighs a ton. And they've been in basically continuous manufacture ever since the old days. And they have full 100+ key layouts with a lot of alternative layouts. And they cost a third of the kickstarted model F. And they have replaceable parts. And they don't ping. And I own and love three of them and I might be biased.

I don't know if I ever describe programming as easy, but I know I've told people that coding is "the easy part" of software development. (The hard part is the software engineering. Any idiot can write code, but it takes a particularly attentive, practiced idiot to implement 100kloc in a maintainable, efficient manner.)

It's completely insane. There's no reason to be a workaholic at any age, and there's no excuse for exploiting your employees.

There isn't a kindle version. There is an iPad App version that I can recommend highly.

My local DMV is far more enjoyable to go to than my local car lot.