Sporadic Attempts at Design and Life – Telegram
Sporadic Attempts at Design and Life
513 subscribers
919 photos
180 videos
29 files
319 links
https://bento.me/temdesigns

Title self explanatory. Opinions, resources, works, tools, and memes.

All of the tools i have shared: @temsharestools

Contact @just_tem
When DMing, arrive at your topic in less than 2 texts. Will be reported as spam otherwis
Download Telegram
Fonts to Match the Style, all under google fonts ;)

1. For Logo/Display Text (like “PICCOLO’S”)
• Font: Chewy
• Style: Bouncy, cartoonish, retro
• Best for: Character names, main brand wordmarks
• Alternative: Lilita One
• Slightly more compact and structured, but still retro-bold



2. For Labels/Badges (like “BRINED CUCUMBERS” or “GLUTEN FREE”)
• Font: Chicle
• Has a playful, hand-lettered feel
• Perfect for ingredient tags and flavor badges
• Alternative: Fredoka
• Rounded, modern-vintage look, great legibility



3. For Supporting Text (like ingredients or small notes)
• Font: Quicksand
• Geometric, clean, and soft. Plays well with the friendly branding.
• Alternative: Archivo
• If you want something a bit more structured but still retro.



Tips for Applying the Style
• Use bold weights of these fonts to echo the thick linework in the illustrations.
• Stick to 2–3 font families max to keep the hierarchy clean.
• Use color blocks or strokes to emulate the badge-like shapes around text.
Sporadic Attempts at Design and Life
https://www.youtube.com/watch?v=P9A2NP5DtAA
whoever watched this, I would love to hear your take about this cause idk how to feel about it
All there is is love and work
- Sigmund Freud
POV: you have an obsession with making these balanced
Finally got around to redesigning my awful linkedin banner
🔥5
how it used to look
🔥3
How it looks now
🔥9
Here is what a VP of product design at Intercom had to say about FE and design roles in the near future
Last week, after ten years at Intercom, I shipped my first code change to production. Just a little UI tweak. But it helped crystallise a major belief I'm developing about how design roles will evolve.

I now think that in the near future designers will basically be responsible not just for designing the UI, but for both designing and building the entire frontend. Designers, not Engineers, will inherit product UI.

The old days of designers drawing convincing pictures of user interfaces, which are later recreated by someone else in code, are over. And good riddance: it was inefficient, frustrating, and is thankfully no longer necessary. Soon most frontend engineering tasks will be carried out by designers, with the “handoff” or primary interface between Design and Eng being at the front/back end distinction.

Here’s how I think we’ll get there.

At companies like Intercom today, designers are already approaching frontend ownership from two directions:

1. Ideation. Lots of designers have started vibe coding throwaway prototypes in Lovable et al. This is great! Prototypes are the new wireframes. There is almost zero technical barrier here, every designer can do this today.

2. Dev Mode. A bit better than drawing all your own redline annotations onto static mockups and logging P3 bugs… but only a bit.

You can easily imagine a tool-driven acceleration of each of these:

1. Early build. Instead of a throwaway prototype, vibe coding tools now ingest your Design System, and spit out something built with your actual product components that can be iterated into the final UI.

2. QA and polish. Instead of describing changes in Dev Mode, designers use Cursor etc. to make simple changes to production code, submitting PRs.

(This is the type of change I made this week, and it’s eminently doable for non-Engineers, even in a large/mature codebase like Intercom’s. Every designer at Intercom is going to ship code to production this quarter.)

These two trends—starting to generate the first build of the UI from one side, and nibbling away at quality-of-life changes from the other—are converging at the same place: designers will be responsible for the end to end design and build of the user interface.

Like all predictions this one will be wrong in some very specific ways. But I believe this is directionally what will happen, or at least where an ambitious next generation of designers will gravitate—especially those who value quality, speed, and self-determination. Prepare accordingly!
And while on one side, a lot of friction is about to go away (especially that design to code 10% non adherence),
On the other side, I don’t know how to feel about it. What about technical concepts like DOM, code level accessibility and clean code that designers aren’t trained to write?

Other than that, I was checking out the figma dev mode MCP, which kinda gives models some guard rails… since adherence to design systems, design tokens and stuff of that sort matters and that is where AI is going wrong these days.

I recently built bills.tem.works fully on bolt through prompting alone, yet, that is a standalone quick project and not something that pertains to a large code base with a component set and a predefined design system.

I will need to do my own research and experiment with a real world task where I will be using a combination of cursor, devmode MCP, and one of the front end codegen platforms to actually test this on a real codebase and a real project to check if its legit and also where I actually lie on this spectrum in terms of readiness.
Media is too big
VIEW IN TELEGRAM
Made this yesternight
❤‍🔥3