Plank AI Accelerator launches for early-career engineers

Anusheel BhushanAnusheel Bhushanco-founder of PlankOriginally posted on LinkedIn 

I am excited to announce the launch of the Plank AI Accelerator - a fully-paid, 1-year intensive program for ambitious early-career engineers who are ready to go all in on AI and the future of programming.

AI is fundamentally transforming software development. There is a rapidly growing gap between engineers who leapfrog their abilities using AI and those who don’t. And we aren’t just talking about using codegen and copilots for increased productivity - those are table-stakes at this point. The real opportunity to level-up is in building new types of AI-native features and apps using LLMs (think swarm agent pipelines, voice agents, LORA adapters, on-device models).

That’s why Privahini Bradoo and I created the Plank AI Accelerator - to turbo-charge engineers with advanced AI tools and give them hands-on experience in building the next generation of AI applications.

Applications are now open for our first cohort in Belo Horizonte, Brazil. Spots are limited - learn more and apply here: www.joinplank.com/ai.

Let’s build the future together!

View image
  • Plank

Keep reading

Coding agents

Cursor 0.43 ships agents while GitHub Copilot loses steam

Cursor releases agents within the IDE with their 0.43 release. GitHub had a huge advantage and was moving very fast up until last year's Github Universe. Seems to have totally lost steam since then. - The recent release of PR summaries in Github.com is very poor quality. The summaries have long links to random files in the PR inserted in the response markdown, in addition to just being incomplete and inaccurate - Still no full-repo context in CoPilot - The idea behind VSCode apps was great. It was announced last year - still not released - "Generate unit tests for this PR" feature still not live Microsoft you started from pole position but are now getting lapped!

Software architecture

Why Plank recommends Hex for data analysis and visualization

Highly recommend Hex for data analysis and visualization. Benefits over other similar technologies: - great integration support with most databases as well as platforms like Snowflake, BigQuery etc. - hosted solution so don't have to worry about scaling - you get the benefit of on-demand / lambda type functionality out of the box - python notebooks on the cloud / native SQL support - ability to integrate the generated graphs natively inside user-facing applications We have had success building complex data integrations and visualizations in as little as 1 day with a tech stack combining Hex and DBT.

Models and research

LLMs learn by compression, as Ilya Sutskever argues

I love this video re: LLMs. Its all about compression! The text on the internet is a mapping / representation of all human knowledge. If you compress that, you force structure and the system learns something about the underlying "processes" that produced the text. A simple example is if you compress a bunch of math tables (that have examples of addition/multiplication/division etc etc), the most efficient compression of that data is a calculator function! This should also help people understand that these models are not just statistical prediction machines but truly are able to reverse engineer how things work and hence able to "compose" this understanding to derive "new insights". Once I heard Ilya Sutskever's argument re: compression, it seemed obvious to me in hindsight...wish I had come up with this in 2012 times :) Its also an example of compounding - people who had internalized this early just had a large head start on everyone else. There is a lot of power in relentless pursuit of the most simple yet non-obvious ideas. youtu.be/GI4Tpi48DlA

Software architecture

Missing DTrace from Solaris for tracing live processes

I miss dtrace from Solaris. Dtrace probes would allow you to attach the trace to live running processes, without needing to restart the process. Some things you could check: - print which functions are doing memory, disk allocation or network requests incl the sizes. This was great to catch memory leaks or programs with poor cache performance - trace a specific code function. Using the symbol for the function in the binary, you could print the parameters and function return values - trace the latency of a user request by tracing invocations of functions at the start/end of the processing - performance measurement of modules. Attach the probe for an hour and do a running count of how many times a function was called or how much memory was used on average for a request Linux strace seemed not as powerful. Any other options? brendangregg.com/dtrace.html

Models and researchSoftware architecture

Quantized Llama models make on-device AI apps practical

With the latest quantized Llama models that are just 1.3GB and 3GB in size, you can start doing mobile/desktop apps that download fine tuned models per user/customer and can run fully locally. This makes variable running costs of AI apps zero and moreover achieves maximal data privacy. We are building a few apps with this new awesome architecture. Anyone else doing that? Would love to exchange notes.

Software architecture

When RAG and vector databases are the wrong tool

Common error in app-layer LLM products is that people use RAG and Vector DBs incorrectly. To process a single document or small amount of input information, people first chunk it, throw it in a vectorDB then retrieve it and put in the context. That makes no sense if the original document is small and could literally be fully packaged in the context window. Remember - you need RAG if during inference, you need to select a subset of information from thousands of documents (100s of millions or billions of tokens), which of course is impossible to include in the context window of a single inference.

All postsOlder posts