Leo Creatini

"I don't like leetcode style interviews!" See I wasn't making it up! Kurtis Nusbaum tells us more about why engineers don't like leetcode and the types of interviews that lead to a more enjoyable and effective interviewing experience.

4

1 Comment

While some folks hire entire Figma design teams for their personal websites, I'm here at 6:30 AM explaining to my partner why I need a third coffee to "write stuff." 2022: "I'll share monthly insights about building companies!" 2024: checking it -> Writing consistency matches crypto winter performance 📉 But look - AI got better at English faster than I got better at writing. That's what we call product-market fit. New strategy for 2025 - Actually write 12 articles - Convince partner these dawn coffee raids are essential business ops Track my progress (or lack thereof) here: https://lnkd.in/e6bkkxvH P.S. If my partner reads this - yes, this is exactly what I'm doing at 6:00 AM either wiring or reading the book. Note: Will open source my coffee consumption metrics in Q3 2025. Full transparency, like web3 promised.

30

1 Comment

I’ve worked in various industries in different positions for 15+ years, including: • Digital editor when Facebook became mainstream. • Graphic designer for traditional mediums. • Front-end dev with top NYC creative agencies. • Web3 dev who survived the bear market. I’ve had so much fun during this time, and there isn’t much I would change about my journey. However, I burnt out badly twice. The burnout exhausted me, taking away more fun I could’ve enjoyed. If I could go back, here are a few mistakes I made—and what I would have done differently to avoid burnout: 1️⃣ Lack of boundaries I failed to set clear work-life boundaries, leading to overwork and anxiety. The pandemic and remote work made it worse. I should have set specific work and rest hours and a designated work area to ensure proper recovery. 2️⃣ Failed to manage expectations I didn’t communicate effectively with employers and clients, which led to unrealistic goals and deadlines. I should have taken the initiative to discuss workloads and responsibilities with stakeholders regularly. 3️⃣ Objectify myself at work I measured my worth only by my job performance and output. Taking breaks even made me feel guilty and lazy. I should value myself beyond work and reserve time for personal passions. － By addressing these issues, I could have avoided burnout and enjoyed my career journey more. If you’re early in your career or feeling tired, remember to: • Set boundaries • Manage expectations • Value yourself beyond work Good luck with a sustainable and happy career ✨ Read this post and more on my Typeshare Social Blog: https://lnkd.in/gNtEeGar

4

2 Comments

I'm looking to talk to someone that works for an organization that offers a paid developer plan in addition to their "standard" product (the main product sold can't be sold directly to devs). Essentially I'm looking to understand how companies think about monetizing that type of product. If that is you or someone you know, please point them my way! #developerplans

9

The open source team I'm a volunteer for at Couchers.org is looking for (volunteer) UI/UX Designers. Come join us, we're fun! Our Figma designs can't keep up with our engineers...halp? Maybe you're taking a sabbatical and want something on your resume for that time. Maybe you wanna see what it's like to work on a project that has nothing to do with stakeholders or investors, where we just do stuff our users want and we think is cool. Maybe you're passionate about traveling and old school couchsurfing vibes and wanna nerd out about it on a team with other travelers. Or maybe you just love designing stuff and are looking for some public portfolio pieces? Join our volunteer team! More info here: https://lnkd.in/g_PwevB9 On a side note, if you're a software engineer with some experience in Javascript or Python and looking for a fun project, we're always looking for more people too. (Please I need more people to review my PRs lol). #uxdesign #uxui #figma #design #opensource #volunteer

13

2 Comments

Our next React Native Boston meetup is just over a week away! Join us at Flexcar’s office in Seaport on Wednesday, December 11th, at 6:00 PM for an evening of talks, knowledge sharing, and networking. We’ve got an exciting lineup of talks: 🎙 Sean Sanker Jr: Intro to Skia and Shaders An introduction to React Native Skia and Shaders. We’ll walk through what Skia is, what Shaders are, the basics of using both, and how to use them together. 🎙 Joseph O'Shea:  React Query | Data fetching made easy An introduction to React Query: what it is, how it can make React Native development easier, and why you should use it. We will demonstrate how to get started with React Query in your app including setup and common usage patterns. We'll also outline some of the more advanced functionalities and give guidance on where to learn more about advanced patterns and use cases. 🎙 Me: GraphQL to REST | Leveraging Zod for Type Safety An overview of transitioning from GraphQL to REST: the motivation behind the switch and how we leveraged Zod to maintain the type safety we had in GraphQL without writing a lot of code. This is a great opportunity to learn, connect, and be part of Boston’s React Native community. Light refreshments will be provided. 🔗 RSVP now to secure your spot and be added to the building’s security list (required for entry). RSVPs close at noon on the day of the event. We’re still actively looking for food sponsors to help make the event even better! If you're interested, please reach out—we’d love your support. Looking forward to seeing you there! #ReactNative #TechMeetup #Boston #MobileDevelopment #Networking

5

When you build design systems for a living, sometimes you get the satisfaction of seeing other engineers building better UIs with maybe a bit more of their sanity left intact. Other times, your CEO goes goblin mode and makes Windows XP and vaporwave skins using your theming system. 😂

7

1 Comment

Excited to share Starknet's core values that drive their ethos! 🌟 Lasting Broadness: Broad power distribution is key for legitimacy, ensuring operations and decision-making remain inclusive and transparent. Centralized operation, if needed, should be brief. 🔓 Neutrality: Starknet supports societal functions impartially, leaving creators in charge. It remains neutral towards user transactions without censorship. 💪 Individual Empowerment: Starknet thrives on an autonomous and informed user base. Education and adherence to core values are central to empowering users. Starknet's principles are defined by openness, inclusivity, and empowerment, ensuring a strong foundation for all stakeholders. Starknet Foundation #keepitstrange

1

As some of you may know, I will be releasing Traverse on the 28th of August. So, what exactly is Traverse? Imagine a vibrant social media platform crafted exclusively for travelers. With Traverse, you can document, track, and relive every one of your incredible journeys. It’s your go-to place to share your adventures, pinpoint the countries and cities you’ve explored, and visually map your travels alongside your friends'. But there's more – much more. You can also share your upcoming travel plans, dream itineraries, and even find fellow travelers to join you on your next adventure. Perfect for solo travelers looking to make new connections! Excited? Visit our landing page, join the waitlist, and be among the first to experience Traverse. https://traversego.com/ (It seems as though LinkedIn got rid of hyperlinks)

28

3 Comments

Today we're launching our newest candidate quality-of-life feature on Ropes - IDE themes. There's a universal dislike for the rigid IDEs that assessment co's force on candidates. These code editors are slow, clunky, and missing the styes/shortcuts that developers enjoy. Developers are unique, and we work in unique ways. Ropes offers two new options to let candidates keep their style: (1) First, many employers on Ropes allow candidates to work in their own IDEs entirely. We've developed a way to gather insights like you were in the room, while allowing developers to use their daily environments. (2) For cases that need a browser-based IDE - we're giving the ability for candidates to choose their style/editor setup before the assessment starts - so they're comfortable when it begins. --- My bet is that if we build a great experience for candidates, we'll be building a great platform for evaluators, too. I hope you'll follow along as we pursue that mission - and we need help! We're hiring founding engineers in NYC - if you're interested, I'd love to talk to you.

47

Dev agencies, if you don’t want to be treated as a commodity, stop acting like one. - Learn the business context for engineering needs - Stop squeezing your clients every opportunity you get - Prioritize transparency, communication, and accountability In short, position yourself as a partner that uses tech to solve business problems. You really can’t complain about being seen as a commodity if you treat everything as a transaction.

1

1 Comment

NEW: Internal Threads Internal threads allow you to spin up conversations in Slack from Pylon. It's great when you want to start a conversation with someone, but they primarily use Slack (e.g. engineers, product people or anyone who isn't living out of the support system). Common internal threads we are creating at Pylon: 1/ #bugs to report a potential bug 2/ #project channels to ask a team a question about a specific feature 3/ #feedback to report product feedback to the team It's been one of the most game-changing features we've released and we're so excited to share it with everyone. Enjoy!

44

3 Comments

Hey friends - have you used Kafka and can share pain points & feelings on usability? I have a friend working on a project to improve the dev-friendliness and would love to chat (just 15-30 mins) if you're open to it -- comment below :)

4

Need to request files from clients? It’s super easy with the new File Requests feature! Go check it out.

16

At InVision, we worked with some amazing software vendors. I know I've talked about most of these in the past; but, I just want to give a final shout-out to some of my favorites: * LaunchDarkly - feature flags completely changed the way we approached product development. And, allowed us to all but eliminate our incidents and outages (shameless plug for my own book: https://lnkd.in/ehxiy6bY). * Postmark - delivered all of our outbound emails and powered our inbound reply-by-email workflows with flawless uptime and befuddling performance. * Pusher - powered our real-time collaboration via WebSockets, bringing our UIs to life and keeping browsers synchronized. * Intergral | FusionReactor APM - gave us deep insights into our JVM performance, allowing us to track down SQL, API, and processing bottlenecks. * Datadog - truly world-class metrics, alerting, and monitoring. * Adobe ColdFusion / Lucee CFML - the programming language and application server that allowed us to move fast, keep things simple, respond to users, and build wonderful things. * Cloudflare - your CDN, WAF, and web workers took a beating so that our origin servers could stay online. * Amplitude - connected me to the users by giving us insight into what our users were actually doing (or not doing). At one point, I think we had over 300 different SaaS subscriptions; so this list is faaaaar from exhaustive. And, I'm sure I'm forgetting other beloved services. And, many of our teams worked with entirely different technologies. This is just my little corner of the organization. And, I couldn't have done it without them. Thank you so much! ❤️

113

18 Comments

Yesterday, I had to work _directly_ on my MacBookPro for a bit. Usually I work on an external monitor. It's kind of shocking how little screen real estate there is on the laptop itself. It definitely gives me pause when considering UI design. As a dev, it's hard to imagine working directly on the computer. But, I know that's how a lot of non-developer people work. I wish the Chrome Dev Tools device simulator had sizes for laptop devices so I could keep laptops front-of-mind. Seems strange that they only have mobile devices. What are people using these days to at least consider laptop design?

19

7 Comments

We like writing engineering content Our engineers are at the center of what we build and our accountants experience. We're defining what AI-native looks like for accounting. We like writing engineering content because we want engineers who join us to know how we think about problems. This week, our very own Matthew Duong wrote a piece on Single Sign-On (SSO), breaking down the essentials and actionable tips (link in the comments) For founders, improving the login process and making it easier to access your platform means a simpler experience. For enterprises, it means reducing the number of passwords users need to remember, reducing the risk of security breaches. Shout out to Amer Taleb who joined us recently and took our content game to a new level. We have a lot more coming soon: new product features, employee spotlights, and our view of the AI Accounting space. Happy Friday from everyone at Truewind!

36

2 Comments

As a former engineering manager, I’ve been here more times than I care to admit. What looked like a quick, low-cost design change turned into a lot more than we bargained for. Compiling a list of the things that need to be changed (i.e. engineering documentation and physical widgets) always looks relatively easy. But invariably a few things get missed. And some of ‘misses’ can have a big impact on cost to implement the change not to mention the implementation schedule. Coming up with an accurate list of the engineering data that needs to be changed (or created) is a little easier with the right software. If you’d like more insight into how our Tina5s can help, reach out!   #Engineering #engineeringchangemanagement #changemanagement #Tina5s

1