Google Brain founder, Andrew Ng:
"Prompting will die in 6 months.
Loops and Graphs are what's replacing it."
In 2 hours, he shows exactly what the best engineers already build instead, and how to start building it yourself.
The missing piece most people skip: how to connect those loops into a graph that compounds every time it runs.
Watch it, then read the full guide on loops and graphs below.
Alright, here it it after literally years of tinkering, months of research and weeks of writing, re-rewriting, editing, cutting and incorporating feedback, my piece on the Four “Real-World” Foundational Engineering Manager Archetypes is out!
Link 👇
A conversation I have frequently about ACH speeds.
Me: The most important factor to understand is Reg E and the broader constellation that makes banks liable for consumer accounts being drained.
X: But other nations manage this without slowing down bank transfers.
Me: Which one.
A conversation I have frequently about ACH speeds.
Me: The most important factor to understand is Reg E and the broader constellation that makes banks liable for consumer accounts being drained.
X: But other nations manage this without slowing down bank transfers.
Me: Which one.
After careful consideration, I am honored to announce my commitment to the United States Naval Academy. I am thankful to Coach Newberry, Coach Volker, Coach Hall and Coach MacDonald for this amazing opportunity to serve my country and play the game I love. I also want to thank my parents, Coach Spagnolo and the Iona Prep family for all they have done to prepare me for this next step in my life. #committed #fearthegoat #GoNavy #BeatArmy
@ionafootball@Joespags12@CoachMoffitt@_CoachNew@D_WallCoach@JMacDonald_Navy @RivalsFriedman
This use case is is really big. Maintaining documentation is hard...it goes stale quick. This could generate new and help you detect what is wrong. So many possibilities
How to understand Github code repos with LLMs in 2 mins.
Even after 10yrs of engineering, dissecting a large codebase is daunting.
1 Dump the code into one big file
2 Feed it to Gemini-1.5Pro (2M context)
3 Ask it anything.
Here's, I dissect DeepFaceLab, a deepfake repo:
1/11
OK, the title is a little long but hear me out because @UConnWBB and @UConnMBB deserve the recognition.
In honor of both @UConnHuskies basketball teams advancing to the NCAA Final Four, I am proclaiming this weekend in their honor.
I urge everyone to support the Huskies! 🏀
This is Scott Wu.
10 days ago, he launched "Devin", the first-ever AI software engineer & it's insane.
It took the tech world by surprise.
Here are 7 most-shocking things Devin can do:
Top Architectural Styles.
The method to download the high-resolution image is available at the end.
In software development, architecture plays a crucial role in shaping the structure and behavior of software systems. It provides a blueprint for system design, detailing how components interact with each other to deliver specific functionality. They also offer solutions to common problems, saving time and effort and leading to more robust and maintainable systems.
However, with the vast array of architectural styles and patterns available, it can take time to discern which approach best suits a particular project or system. Aims to shed light on these concepts, helping you make informed decisions in your architectural endeavors.
To help you navigate the vast landscape of architectural styles and patterns, there is a cheat sheet that encapsulates all. This cheat sheet is a handy reference guide that you can use to quickly recall the main characteristics of each architectural style and pattern.
–
Subscribe to our newsletter to download the 𝐡𝐢𝐠𝐡 𝐫𝐞𝐬𝐨𝐥𝐮𝐭𝐢𝐨𝐧 𝐢𝐦𝐚𝐠𝐞. After signing up, find the download link on the success page: https://t.co/ito2aWqd62
Ten Principles for Growth as an Engineer by Dan Heller:
“These are the most important lessons that I wish I had learned ears earlier than I did; I sure wish someone had sent it to me when I was 22.”
1. Reason about business value: Reason like a CEO. Understand the value of your work to your company, and take responsibility for reasoning about quality, feature richness, and speed. Your job isn't just to write code; your job is to make good decisions and help your company succeed, and that requires understanding what really matters.
2. Unblock yourself: Learn to never, ever accept being blocked; find a way by persuasion, escalation, or technical creativity. Again, your job isn't just to write the code and wait for everything else to fall into place; your job is to figure out how to create value with your efforts.
3. Take initiative: The most common misconception in software is that there are grown-ups out there who are on top of things. Own your team's and company's mission. Don't wait to be told; think about what needs doing and do it or advocate for it. Managers depend on the creativity and intelligence of their engineers, not figuring it all out themselves.
4. Improve your writing: Crisp technical writing eases collaboration and greatly improves your ability to persuade, inform, and teach. Remember who your audience is and what they know, write clearly and concisely, and almost al-wavs include a tl;dr above the fold
5. Own your project management: Understand the dependency graph for your project, ensure key pieces have owners, write good summaries of plans and status, and proactively inform stakcholders of plans and progress. Practice running meetings! All this enables you to take on much bigger projects and is great preparation for leadership.