App for developing on iPad
Anyone know a good iPad app for remote development? Need something with multi windows feature (Stage Manager), SSH, a decent code editor, and ideally some git support. Tired of switching between 3 different apps.
Anyone know a good iPad app for remote development? Need something with multi windows feature (Stage Manager), SSH, a decent code editor, and ideally some git support. Tired of switching between 3 different apps.
Hi guys,
I'm a Junior Frontend Engineer (Angular) with around 2 YOE.
Last week, I got laid off from a startup. I had already started applying for jobs back in November 2025 when I began noticing red flags due to team restructuring, but so far I’ve barely received any responses apart from 2 screening calls.
I’m applying through multiple platforms including LinkedIn, Naukri, Indeed, Instahyre, Cutshort, Wellfound, and company career pages. I also checked my resume ATS score across different platforms to make sure that wasn’t the issue, and it consistently scores above 85.
One thing I’ve noticed is that the Angular job market seems much smaller compared to React. At this point, I’m confused about whether I should:
• Continue focusing mainly on Angular and keep applying, or
• Spend the next couple of months learning React, build a few projects, and apply for jobs in parallel.
Would really appreciate suggestions from people who’ve been in a similar situation or are currently hiring/frontend devs themselves.
P.S. If this isn’t the right sub for this post, please suggest better ones where I can ask this.
Hi All, recently I just launched a Google Chrome extension that could help developers who are struggling to migrate or extract brand styles from existing sites.
With the launch of Tailwind CSS v4 and its new CSS-variable-first configuration, I found myself spending too much time in the DevTools "Inspect" element trying to dig out variables, color palettes, and spacing scales just to build a new v4 configuration.
So I built Twift to automate that entire workflow.
https://chromewebstore.google.com/detail/twift/nnejighghchkkhogfpelddhmiiklmnbp
I'm looking for the fastest framework in the Krausest "JS Framework Benchmark" Top 15 that doesn't feel like writing assembly.
Goal: Framework performance with a clean, modern DX. I want to avoid heavy abstractions, especially since I'm using AI to scaffold logic and I need the code to be short, readable, and easy to audit.
Of the top 15, which one feels like a "real" framework but keeps the code lean and fast?
I'd appreciate some recommendations.
As a web developer, I often build or collect small frontend assets that are useful later: buttons, gradients, loaders, hover effects, CTAs, footers, bento grids, layout fragments and product UI patterns.
The problem is that these assets usually end up scattered across old projects, screenshots, notes, CodePens, local folders or random files. When I need one, I know I already made something similar, but finding it takes too long.
So I built UI IP Toolkit: a static visual catalog for fast access to my copy-ready frontend assets.
Live site: https://ui-ip-toolkit.vercel.app/ GitHub: https://github.com/ikerperez12/UI-IP-Toolkit-v4.0
UI IP Toolkit is a public, static frontend asset library. It is designed to be browsed visually, not as a package install.
It includes sections for:
Every card is meant to be practical: open the site, scan visually, copy the snippet, adapt it, and move on.
I wanted the toolkit to be simple, fast and easy to publish:
The goal was not to create a huge npm package or a rigid design system. I wanted a personal working library that feels visual and fast enough to use during real frontend work.
When I am building a new page or feature, I can open the toolkit and quickly find a starting point:
It is basically a visual memory layer for reusable frontend work.
The project is intentionally simple:
The repository is public here:
https://github.com/ikerperez12/UI-IP-Toolkit-v4.0
The live version is here:
https://ui-ip-toolkit.vercel.app/
The biggest improvement was not adding more components. It was making the catalog easier to navigate.
Once the toolkit had many sections, a long top nav became useless. I replaced it with a compact section menu grouped by category. That made the site feel much more like a real working tool instead of a long landing page.
I also learned that previews matter a lot. If every card looks too similar, the library feels bigger than it is useful. So I spent time making the previews more varied and more realistic while keeping the site lightweight.
I am sharing this because I think other frontend developers might have the same problem: useful assets scattered everywhere, but no quick visual way to reuse them.
Would you use a personal visual asset catalog like this in your own workflow? And what sections would you add next?
Live site: https://ui-ip-toolkit.vercel.app/ GitHub: https://github.com/ikerperez12/UI-IP-Toolkit-v4.0
He creado E36 Scroll Cine, una experiencia web cinematográfica fan-made sobre el BMW 318is Coupé Pack M (E36).
Web: https://e36.vercel.app/
GitHub: https://github.com/ikerperez12/e36
La idea no era hacer una landing normal, sino algo que se sintiera más como una pieza visual vertical. Empiezas en una pantalla de entrada con vídeo y después avanzas por siete escenas usando scroll, teclado o gestos en móvil.
Cada escena está centrada en una parte del coche:
He intentado que el contenido hable del coche de verdad, no de frases genéricas. La ficha y el HUD incluyen datos del 318is: M44B19, 1.895 cc, 16 válvulas DOHC, Bosch Motronic M5.2, admisión DISA, Getrag 250G, reparto 50/50, suspensión Pack M, etc.
En la parte técnica, la web es bastante simple:
No es una web oficial de BMW. Es una fanpage y un experimento web alrededor de un coche que me gusta mucho.
Me encantaría recibir feedback:
¿La experiencia se siente bien en móvil? Y si conocéis bien el E36/318is, ¿qué dato añadiríais o corregiríais?
Had 24 hrs to submit an assignment for senior front end role but recruiter is OOO and engineering team already cloned the repo, had a few ideas to make it better should I do the changes in a different branch by tomorrow and just send an email to the team or just let it go? Anyone had any experience on something like this?