nahname

It is a lot like reading levels. Go feels like a grade 5 reading level. This means most people can read it. It also means complex concepts take a lot longer to explain because you have to avoid all sophistication.

There are people who cannot use an abstraction unless they understand every line of code behind it. Abstractions are blockers, rather than aids. This lowers the value of abstraction for those individuals.

Others find it tiresome to read every line of code and develop intuition around abstractions instead. The "find_definition" function will be all that is parsed.

The funny thing is people shift between the two as the scope of the project increases.

Whataboutism does not add to the discussion.

In a natural conversation, it is rare to have someone stair you in the eyes for more than a couple seconds.

Hadn't considered that for some, this constant stair feels like they are finally being recognized. This makes a lot of sense. You wait for your turn to talk and the stage is yours. In some sense, everything is fairer.

>I do miss the days of ‘cap deploy’ for Rails apps.

Add operators, complicated deployment orchestration and more sophisticated infrastructure... It is hard to know if things are failing from a change I made or just because there are so many things changing all the time.

Or the ISPs don't throttle traffic to fast.com

This is a sad truth

If there is nothing to discuss, reduce the cadence. It is the employees meeting, not the managers.

If the manager is powerless to address the issues or clarify them, then that is a failing of the manager.

It's 30mins once a week or an hour every two. For an IC, this may be one of your only meetings.

Have heard similar estimates, found an article corroborating this.

https://www.theglobeandmail.com/business/article-unemploymen...

I know people who joined post IPO and make more than that at Shopify as Senior Developers. Is primarily equity though. Salaries do lag in Canada vs USA.

Sure didn't help that 2018 ended with everything being down 15-20%, this year was more of a rebound than a continuous healthy market.

>...problem is that often developers and management (at all levels) give very little thought into "delivering value"

That sounds like a cultural problem. From my experience, tools do not solve cultural problems. Leadership changes cultural problems.

Excellent point. It isn't to say that the developers cannot learn modern practices. I know this is how I worked when I first started and am a moderately capable developer. It is an undertaking though.

Is going through that gauntlet fairly universal? Onboarding is almost always a pain for the individual if you are hiring outside of large tech companies. Why is our default coding style not compatible with team programming?

Recently refactored some of our yaml/erb and it worked out quite well for us. With the addition of fixtures to show current vs next form of the entire yaml, it has made altering our cluster much easier to follow and keep changes consistent.

As long as software is a cost center to your company, it will be treated this way. Trying getting a job at a company where software is a core concern. Ideally with a CEO that is not from a marketing/business background.

It is a pretty common feature of languages since smalltalk. IMO when people say go is missing generics, this is what they are referring to.

Canada definitely does not have more guns per capita. USA is the highest in the world. https://en.wikipedia.org/wiki/Estimated_number_of_civilian_g...

Aurora requires a VPC, but you can create public subnets to allow for external access to the database.

https://docs.aws.amazon.com/AmazonECS/latest/developerguide/...

The work that goes into "external code" is higher quality than most companies can achieve. The cost of developing a similar tool may also be outside what the company can afford to invest.

If your business is online schema changes, then inventing it yourself makes sense. Otherwise you are likely throwing money away to create an inferior product.

Though that would still be idiomatic go code. For what it is worth, I do agree with you. Short variable names on a function are a hassle. You have to lookup what they mean, which slows down understanding.

n = copy(p, b.buf[b.r:b.w])

Oh better go to the top and see what those are again...

https://github.com/golang/go/blob/master/src/bufio/bufio.go#...

>To reduce cognitive load, I want to be able to read a function/method without having to think about where some variable comes from.

To reduce cognitive load for me, I should be able to treat the function/method as a black box. Care about what it receives, care about what it returns, don't care about how it goes about accomplishing it.

>When I read the code above, my first question is: How is config.Pi defined?

That line really hammers home the difference. I trust the previous author, the test suite and ultimately, the project. Programmers seem to fall into two camps. Those that need to know details to understand a method and those that need to know the contract to understand a method.

>This is well known. Relative social status has an influence on health.

You mean outside of health choices made for financial reasons? That was news to me. Simply being in bottom hurts you, even if you are doing everything else the same.

So simple anyone with at least three to five years experience and 4 months on the project can do it! Starting salary is 120k, relo to SF required.

>The first time I visited Google, they had about 500 people, the same number Yahoo had when I went to work there. But boy did things seem different. It was still very much a hacker-centric culture. I remember talking to some programmers in the cafeteria about the problem of gaming search results (now known as SEO), and they asked "what should we do?" Programmers at Yahoo wouldn't have asked that. Theirs was not to reason why; theirs was to build what product managers spec'd. I remember coming away from Google thinking "Wow, it's still a startup."

A desire and the ability to own problems is difficult to bring back once it is lost.

Can I have access to your email account? I only want to read everything you don't care about protecting. Promise.

Cost of living is much less in the US than Canada.

Definitely sounds like a cultural mismatch between your work environment and the expected github work environment.

There is a surprisingly wide area of coverage for something titled "Front-end Developer Handbook". I also like the way the content is presented (not the technology used).

The JS testing section is a good example. Pertinent summary of high level concepts before the fold. Additional content to read if you want to learn more.

https://frontendmasters.gitbooks.io/front-end-handbook/conte...

Edit:

By technology, I mean using a SPA for docs is silly. Not surprised the mobile experience is poor because of that.

I would be buying a home (or two) if 300k was the price tag.

Is the problem a function of the size each PR is? If each PR is small, it shouldn't take much time to review.