zakm
Here's a short video demo if anyone is interested: https://youtu.be/owuuFxDBQh4
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).
The Trap of the Premature Senior (2020)
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 [email protected]
Ask HN: High level market analysis for entrepreneurs?
As an entrepreneur who builds software, it would be nice to know some high-level data like: 1) What are the different sectors of the economy ranked by GDP? 2) To what degree has software penetrated those sectors? 3) What barriers exist in those sectors? 4) Are those sectors growing, shrinking, or staying the same?Obviously, (1) is answered and I'm sure people have written about the other...
Honeypot.io for VC Investment?
Seems like everyone complains about going from VC to VC with all these pitches.Why not invert the marketplace (in the same way that honeypot.io did for developers)?As startup founders, you write up all the info that a VC would want to know. Maybe some of it is public and some is not. VCs who are interested reach out.Marketplace makes money when deals get made (so incentives are aligned), or...
I'm glad we try to understand the world and bend it to our will.
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).
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?"
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