HN user

zakm

44 karma
Posts4
Comments27
View on HN
[dead] 1 year ago

Going against the grain here, but personally as I've gotten more experience and worked in larger code bases I've completely reversed my habit of breaking functions up into smaller functions to supposedly make them easier to understand.

The only argument I can think of against this would be that it would maybe slightly discourage adding the verbose details and would generally decrease the quality of error messages slightly. That said, even so it's probably worth the trade.

It's worth considering that in the networking example given you discover the skills you need via a project and then argue that the skills could be learned more effectively through deliberate practice.

I think this post largely argues against a strawman (which I'm sure some people actually believe).

Seems fairly clear to me that you should (1) do projects that resemble the work you're trying to improve to: a. Build up the basics across all the skills you need b. Uncover gaps

And (2) then practice the skills you actually care to improve outside of the project.

If you really want to try-hard you can spend time actively thinking about how to improve what you're doing and observe other people to learn from them.

People who advocate project-based learning have generally experienced spending a ton of time learning things in theory and then being unprepared for actual work. Maybe address that concern instead of bypassing it with "I don’t want to debate the current way universities do things." To have a nuanced take you have to understand the arguments in favor and against the main options, no?

I don't think people who advocate for project-based learning are advocating for exclusively project-based learning (mostly).

Plotly | Full-time | REMOTE, (CA or US) | https://plotly.com/

Looking for a senior backend engineer.

We're building Dash Enterprise, a web app that lets data scientists quickly and easily spin up and scale data science and ML apps. We do this using Kubernetes. Cool, right?

Reasons to join:

* Cool technologies like Kafka, Kubernetes, NestJS, and CockroachDB.

* Good pay (well above market).

* You'll spend 60-90% of your day programming.

* You won't work overtime.

* Plotly is a major supporter of open source (plotly.js and dash).

* Customers like Tesla, Shell, Cisco, and Nvidia.

* All the cool parts of working at a startup. Autonomy, impact, moving quickly.

* Dedicated time to learn every day (part of your 8 hours).

* New codebase!

What we're looking for:

Experience: 5+ years developing software. Strong with Node.js. Ideally familiar with NestJS, GraphQL, Kafka, Kubernetes, and/or event-driven architecture.

Table stakes: Familiar with git, pull requests, SQL, API design, automated testing, and writing clean/maintainable code.

Personality: You should be self-directed, comfortable diving into something you don't fully understand, friendly, and deeply care about doing a good job.

Email resumes to zakmiller@plot.ly

I'm sure what you're talking about happens (although I personally haven't seen it). What also happens is that cultural differences lead to two people having different perceptions of the same event. One views it as "honest and blunt" and the other views it as "rude." I think a lot of the pushback comes from people who have personally delivered things they view as "honest and blunt" and have had others say that they are being "rude" or "mean-spirited," and they view things like this CoC as a push by the thin-skinned to institutionalizing niceness at the expense of honesty.

Other examples of us trying to rationalize and systematize chaos: "the heliocentric model of the solar system", "physics", "economics", and "science."

I'm glad we try to understand the world and bend it to our will.

My belief is so self-evident that anyone who comes into contact with it must agree with it, therefore if someone doesn't agree with me it must be because they haven't come into contact with it, and the idea is everywhere so therefore if they haven't come into contact with it they must not be open-minded!

There won't be a war, by the way. I honestly think we're past the point as a species where superpowers duke it out in such a literal fashion. It's just bad for business.

I tried to find the quote and couldn't, but IIRC this exact argument was used for why WW1 never could have happened (prior to WW1).

Or maybe the company is seeking out women in particular.

If there was a company that was made up of 90% men when the workforce was 50%, would you say that "plenty of men independently decided that that company was a great place to work in?"

a) Trying to understand historical events with many variables via deliberate scientific experimentation is a reasonable thing to do.

b) The Stanford Prison Experiment has always been under a ton of scrutiny, and is a good example of flashy events heavily covered in intro psych courses that are viewed with a lot more skepticism in the professional community (so I have read, anyway).

c) More info recently came out about it recently, actually: https://cosmosmagazine.com/social-sciences/new-evidence-show...

d) Repetition of scientific findings is one of the main pillars of science. See: https://en.wikipedia.org/wiki/Replication_crisis