the HN thread has a lot more papers: https://news.ycombinator.com/item?id=27892076
- Out of the Tar Pit 2005, a paper on Functional Reactive Programming that is an excellent read for anyone doing functional programming, UI programming, or a number of other things.
- Consistent Hashing and Random Trees: Distributed Caching Protocols for Relieving Hot Spots on the World Wide Web 1997, important read for anyone working in distributed systems or services with any sort of scale.
- Roy Fielding's dissertation 2000, to learn just how widely applicable REST principles are and how misunderstood it is as a design.
- The Part Time Parliament 1998, the original Paxos paper, important basis for anyone working with distributed systems.
- The Cathedral and the Bazaar 1997, an essay not a paper, but a good background to the open source world.
- What every computer scientist should know and floating-point arithmetic - 1991
- Programming as Theory Building - Peter Naur
- Computing Machinery and Intelligence - Alan Turing - 1950
- A Mathematical Theory of Communication - Claude Shannon
Just read the CFP chapter of the book. A mentor (and predecessor on my current team) recommended that I try to speak at EmberFest.
I'm the only frontend dev inheriting 65K lines of Ember code (I've never written in Ember). Learning Ember has a steep learning curve and I'm developing a set of mental models to shorten that curve.
Would love some feedback on my CFP.
- Has to be genuinely new category
- Has to be simple terms
- You want to have competitors - expansive enough to let people draft off of
- Define the picture, define the market - marketecture diagram
- How I transitioned from humanistic jobs to tech and development (1/3)
- My first six months working as a (self-taught) developer (2/3)
- How I passed from Junior to Intermediate developer in one year (3/3)
There are many out there (I talked to many as well) who made the shift to development after many types of non technical at all careers (like humanistic or others) so I hope they'll help them understand that it's totally feasible.
I talk about what I learnt by my mistakes and progress. I'm trying to make it public so that more psychological barriers will come down.
If anybody can give me any feedback it'll be greatly appreciated.
She identifies 6 main causes of burnout:
- Workplace community: All the people whose paths you cross at various points—you know, coworkers, the people you supervise, your bosses, et cetera—so those social relationships, that culture, do you have a supportive environment which really helps people thrive? Can you trust people, there’s respect, and all that kind of thing going on? Or is it really what people are now describing as a socially toxic work environment?
Reward: not so much salary and benefits, it’s more about social recognition and the intrinsic reward you get from doing a good job. So, if you work hard, do some special things, and nothing positive happens—nobody even pats you on the back, nobody says, “Gee, why don’t you try this new project? I think you’re really good at it,” anything that acknowledges what you’ve done—it’s a very difficult environment to work in.
- People who are more at risk of burnout, when I asked them, “What is a good day for you? A good day. A really good day.” And the answer is often, “Nothing bad happens.”
- Values: you’re doing work that you think is meaningful, where you’re working has integrity, and you’re in line with that as opposed to value conflicts and where you’re doing things that you think are wrong: “I want to help people, I want to help cure patients, and here, I’m actually only supposed to be trying to help the hospital get more money.” When they have that kind of value conflict, this is often where they have to say, “I don’t want to sell my soul and I’m leaving.”
- Fairness: when things are going badly here—the mismatch—this is where discrimination lives, this is where glass ceilings are going on, that people are not being treated fairly in terms of the work they do, how they’re promoted
- Workload: Given the demands that you have, do you have sufficient resources, like time, and tools, and whatever other kind of teams support you need to get the job done.
- Control: the amount of autonomy and the opportunities you have to perhaps improvise, or innovate, or correct, or figure out how to do the job better in some way.
Just starting out but would love some constructive feedback on
what I've posted so far 🙂
- Her team covers: Compilers, Programming languages & application runtimes, Tools & IDEs, Azure DX
- eg TypeScript, VS, VSCode, .NET
- "Everything I work on has to do with the fact that we have a massive developer shortage right now" - estimated 150 million tech/tech adjacent jobs in the next 5 years, vs <10m professional developers in the US. We need to mint new developers, incl more diversity
- they are teaching Tech Resilience as a focus now
- There is an absolute shortage of educators (eg professors and TAs) - because everyone moves into industry - they are working with Mt Holyoake to produce content on this stuff including growth mindset
- Memorizing is outdated - search can answer all these questions
- Knowledge base - tribal knowledge
Importance of open source
- allows you to build on the shoulders of giants. Focus on code that only you can write
- Great for learning - learn how other people write code, learn how to help teams scale
- But it brings everyone into your supply chain - so security is a problem. solving with dependabot
- Microsoft's new approach to open source - started with TypeScript.
- Took at least a summer to get approval to open source TS, now everything is default OSS
- Microsoft Learn & Global Skills Initiative with certifications
- Codespaces - help developer velocity by provisioning dev machines. turn dev machines from pets to cattle.
2. Create/draw an Illustrated Guide to some foundational industry topic
3. Understand that everything is a Remix.
Nothing is created completely originally. Copy, then tweak.
For example, you can copy other UI's and tweet what you do and learn as you go:
I'm challenging myself to recreate UI elements from around the web as a way to learn new things and keep fresh. 🍋— Delba de Oliveira (@delba_oliveira) June 13, 2021
Here's a wip thread on what I've been building, using and learning:
🏗️ Base stack:
• PostgreSQL and @Prismahttps://t.co/TSg7oLUAIy
4. This career advice tweet thread.
7: whatever you do, document it in writing, ideally in public. It’s a HUGE force multiplier on your reputation and helps other ppl build on your work— Sarah Constantin (@s_r_constantin) June 16, 2021
5. Create the resource for something you need to self study anyway