Hey, I hope it's fine to share open source book on a11y, comes with 61 CodeSandboxes you can just tap & play -> https://github.com/Ditectrev/Awesome-A11Y-Book-Course-Web-Accessibility-A11Y (no need to buy anything, content is the same, just different format is paid)
We've lots of open source materials, so no scam ;=)
- Module Federation provides better performance, but no strong runtime isolation.
- iframes provide strong isolation, making independent deployment more reliable.
- This matters especially for large, legacy codebases where enforcing boundaries in code is difficult.
- A typed communication SDK, routing, and smart chunk splitting can reduce the performance cost.
- For large legacy applications, iframes can be a better tradeoff than MF
i want to prepare for sr data scientist in MAANG companies. My background is in core ML, deeplearning, nlp etc.
I plan to target in around a year from now.
Does someone have any idea about the interview preparation or someone in these companies who would like to share some experience?
Interviewprep resource:
PracHub: Company specific interview questions
DataLemur: SQL Interview and Data Science Interview questions
StrataScratch: SQL and Python interview
Well, i just wanted to make a simple cooking game, with rules and so on, for my tortilla de patatas project.
let the ai loose in the loop and "we" are building this: https://github.com/felixinberlin/openCulinaryRuntime
Its like a set of cooking rules.
Very complicated and scientific.
if someone is interested in the idea just pm me.
I need someone who speaks Dutch to whom I am allowed and able to ask questions.
I'd love to receive some feedback on this post I made, especially concerning aspects I may have overlooked.
As for the comment I'm sure I will receive: yes, using a framework is indeed the way to go for a professional solution to SSG. But my goal is to keep as much as possible of the default React setup most starting developers are stuck with and show some of the inner-workings of something that is too often taken for granted.
not looking for the usual extension recommendations i am more curious about tiny built in settings or shortcut you ignored for ages and then wondered how you worked without them
what was yours?
First screenshot is 1366px wide, the third is 412px wide. The second screenshot is a style experiment using real coffee beans instead of the coffee branch illustration (which I could either mix and match both styles across different sections, or just stick to one for the entire website).
The assets here are placeholders for now. Any feedback is welcome!
I have been working with ReactJS primarily, enhancing code (working for MNCs) for the past 6 years so naturally, I feel like there are a lot of gaps. Understanding containers, CI/CD pipeline challenges, Unit testing without AI, handling edge and base cases in Redux (Invalidating a state) among many other things.
Please suggest sources I can study and projects I can create, that will help me understand the overview along with the internals.
This one took a while, it's probably the longest thing I've written on this blog. I wanted to do a proper end-to-end walkthrough of cmd/compile: real package names, real data structures, diagrams for the AST and SSA CFG, and the flags you actually need (-m, -m=2, GOSSAFUNC, -S) to observe each phase yourself rather than just take my word for it.
Covers the full pipeline: lexer → parser → type checker → IR lowering → SSA construction → optimization passes (inlining, escape analysis, BCE, nil check elimination, register allocation) → architecture-specific code emission.
Hope it's useful — happy to answer questions or push back on anything that looks wrong.
AI has changed frontend development a lot. Today, tools can generate React components, write CSS, fix errors, and even turn a design into working code in minutes. It definitely saves time, especially for repetitive work. But I sometimes wonder if this convenience is making developers skip the fundamentals. If AI writes most of the code, how well do we actually understand what is happening underneath?
I think AI is a great tool for frontend developers, but it should make us faster, not replace our understanding of JavaScript, CSS, performance, accessibility, and good UI practices. What do you think? Has AI actually made you a better frontend developer, or just a faster one?
I feel that AI can do really good layouts as long as you explain everything you need really well and thats regardless of the AI you're using (OpenAI, Claude, Kimi, Gemini whatever). But i really struggle to actually make responsive designs with AI. But maybe I'm missing something because everyone seems to think the exact opposite here. I try to optimise for different views but not for someone actually going ahead and shrinking the windows left and right. How do I design for something like this?
I just wanna know if you guys have any tips for approaching all this? Because I think frontend design, at least the CSS should be a piece of cake with AI?
Getting a working UI out of an AI coding assistant is ridiculously easy now. The interesting problem is what happens afterwards. Generated components are easy to create, but keeping a large application consistent, accessible, maintainable, and understandable is still very much a human problem.
It feels like AI is moving the bottleneck in web development rather than removing it. We're spending less time writing individual pieces and more time reviewing architecture and making sure thousands of generated decisions don't slowly turn the codebase into a mess. Wondering if other web developers are seeing the same thing.
Game Title:
Black Imago
Playable Link:
https://blackimago.arewefriends.org/maze
Platform:
Web Browser — Desktop / Keyboard & Mouse
Description:
Black Imago is a free, always-online multiplayer dungeon crawler built around one shared procedural maze. Everyone enters the same canonical sequence of levels, and the known world only extends as players push the global frontier deeper. Right now the community has reached Level 73, meaning Level 74 is still undiscovered.
You explore dark maze levels, fight different enemy types, find exits, encounter other real players, collect temporary abilities and resources, discover secrets, and try to build a run worth keeping alive. Combat leaves blood and physical aftermath behind, and I’m working toward making player actions feel consequential rather than having the game become a simple “run to the exit” loop.
The first large public test exposed a lot of issues with movement, collision, combat feel, multiplayer synchronization, enemy behavior, and performance, so I’ve been doing a major whole-game quality pass since then.
I’m especially looking for blunt feedback on movement, sharp corners, combat weight, enemy behavior, blood/impact, multiplayer smoothness, performance, and whether progressing through the maze actually feels meaningful.
Free to Play Status:
Involvement:
I’m the creator/developer of Black Imago. I’ve been designing and building the game, its shared-world concept, procedural maze systems, multiplayer gameplay, combat, progression, archive/world systems, and the ongoing production-quality pass based on real player feedback.
Content pages in Astro make sense to me. Blogs, marketing pages, docs, easy sell. Once you get into cart state and checkout flows though, does the island model start fighting you, or does it hold up fine?
Curious if anyone has shipped a real store in Astro versus bailing to Next partway through.
Anyone has had a recent experience interviewing at Reddit for a frontend role? I have frontend design interview coming up and I kinda have an idea of what to expect but would love to hear from others experiences. Thanks!