Found 14 bookmarks
Newest
"Design like Apple"
"Design like Apple"
Then find a designer who is a thinker, who has product, customer, and business sense and has the ability to create work for the problem at hand (not just emulate visual trends or other companies). This isn’t a unicorn — this is what good design is.
·rongoldin.substack.com·
"Design like Apple"
Pricing of Webflow freelancers : r/webflow
Pricing of Webflow freelancers : r/webflow
Some good questions to ask: Can they show you some examples of past projects they've built in Webflow? Do some checking if their work looks good on smaller devices (Webflow cascades styles down from desktop, so mobile design can sometimes get overlooked) Are they using a class framework (e.g., Client-first, Mast, Lumos, or custom)? And are they comfortable building the site with a level of modularity that enables easy reuse of sections, components, and styles? This approach simplifies future design updates and makes it easier for your team to manage and expand the site after the handover. What's their approach to SEO in Webflow? What do they do to ensure performance and loading speed are optimized? Do they have a process QA and testing before launching a site? How do they handle client feedback and revisions? Do they have a process for educating you on how to use and manage the site they built?
·reddit.com·
Pricing of Webflow freelancers : r/webflow
The Complex Problem Of Lying For Jobs — Ludicity
The Complex Problem Of Lying For Jobs — Ludicity

Claude summary: Key takeaway Lying on job applications is pervasive in the tech industry due to systemic issues, but it creates an "Infinite Lie Vortex" that erodes integrity and job satisfaction. While honesty may limit short-term opportunities, it's crucial for long-term career fulfillment and ethical work environments.

Summary

  • The author responds to Nat Bennett's article against lying in job interviews, acknowledging its validity while exploring the nuances of the issue.
  • Most people in the tech industry are already lying or misrepresenting themselves on their CVs and in interviews, often through "technically true" statements.
  • The job market is flooded with candidates who are "cosplaying" at engineering, making it difficult for honest, competent individuals to compete.
  • Many employers and interviewers are not seriously engaged in engineering and overlook actual competence in favor of congratulatory conversation and superficial criteria
  • Most tech projects are "default dead," making it challenging for honest candidates to present impressive achievements without embellishment.
  • The author suggests that escaping the "Infinite Lie Vortex" requires building financial security, maintaining low expenses, and cultivating relationships with like-minded professionals.
  • Honesty in job applications may limit short-term opportunities but leads to more fulfilling and ethical work environments in the long run.
  • The author shares personal experiences of navigating the tech job market, including instances of misrepresentation and the challenges of maintaining integrity.
  • The piece concludes with a satirical, honest version of the author's CV, highlighting the absurdity of common resume claims and the value of authenticity.
  • Throughout the article, the author maintains a cynical, humorous tone while addressing serious issues in the tech industry's hiring practices and work culture.
  • The author emphasizes the importance of self-awareness, continuous learning, and valuing personal integrity over financial gain or status.
If your model is "it's okay to lie if I've been lied to" then we're all knee deep in bullshit forever and can never escape Transaction Cost Hell.
Do I agree that entering The Infinite Lie Vortex is wise or good for you spiritually? No, not at all, just look at what it's called.
it is very common practice on the job market to have a CV that obfuscates the reality of your contribution at previous workplaces. Putting aside whether you're a professional web developer because you got paid $20 by your uncle to fix some HTML, the issue with lying lies in the intent behind it. If you have a good idea of what impression you are leaving your interlocutor with, and you are crafting statements such that the image in their head does not map to reality, then you are lying.
Unfortunately thanks to our dear leader's masterful consummation of toxicity and incompetence, the truth of the matter is that: They left their previous job due to burnout related to extensive bullying, which future employers would like to know because they would prefer to blacklist everyone involved to minimize their chances of getting the bad actor. Everyone involved thinks that they were the victim, and an employer does not have access to my direct observations, so this is not even an unreasonable strategy All their projects were failures through no fault of their own, in a market where everyone has "successfully designed and implemented" their data governance initiatives, as indicated previously
What I am trying to say is that I currently believe that there are not enough employers who will appreciate honesty and competence for a strategy of honesty to reliably pay your rent. My concern, with regards to Nat's original article, is that the industry is so primed with nonsense that we effectively have two industries. We have a real engineering market, where people are fairly serious and gather in small conclaves (only two of which I have seen, and one of those was through a blog reader's introduction), and then a gigantic field of people that are cosplaying at engineering. The real market is large in absolute terms, but tiny relative to the number of candidates and companies out there. The fake market is all people that haven't cultivated the discipline to engineer but nonetheless want software engineering salaries and clout.
There are some companies where your interviewer is going to be a reasonable person, and there you can be totally honest. For example, it is a good thing to admit that the last project didn't go that well, because the kind of person that sees the industry for what it is, and who doesn't endorse bullshit, and who works on themselves diligently - that person is going to hear your honesty, and is probably reasonably good at detecting when candidates are revealing just enough fake problems to fake honesty, and then they will hire you. You will both put down your weapons and embrace. This is very rare. A strategy that is based on assuming this happens if you keep repeatedly engaging with random companies on the market is overwhelmingly going to result in a long, long search. For the most part, you will be engaged in a twisted, adversarial game with actors who will relentlessly try to do things like make you say a number first in case you say one that's too low.
Suffice it to say that, if you grin in just the right way and keep a straight face, there is a large class of person that will hear you say "Hah, you know, I'm just reflecting on how nice it is to be in a room full of people who are asking the right questions after all my other terrible interviews." and then they will shake your hand even as they shatter the other one patting themselves on the back at Mach 10. I know, I know, it sounds like that doesn't work but it absolutely does.
Neil Gaiman On Lying People get hired because, somehow, they get hired. In my case I did something which these days would be easy to check, and would get me into trouble, and when I started out, in those pre-internet days, seemed like a sensible career strategy: when I was asked by editors who I'd worked for, I lied. I listed a handful of magazines that sounded likely, and I sounded confident, and I got jobs. I then made it a point of honour to have written something for each of the magazines I'd listed to get that first job, so that I hadn't actually lied, I'd just been chronologically challenged... You get work however you get work.
Nat Bennett, of Start Of This Article fame, writes: If you want to be the kind of person who walks away from your job when you're asked to do something that doesn't fit your values, you need to save money. You need to maintain low fixed expenses. Acting with integrity – or whatever it is that you value – mostly isn't about making the right decision in the moment. It's mostly about the decisions that you make leading up to that moment, that prepare you to be able to make the decision that you feel is right.
As a rough rule, if I've let my relationship with a job deteriorate to the point that I must leave, I have already waited way too long, and will be forced to move to another place that is similarly upsetting.
And that is, of course, what had gradually happened. I very painfully navigated the immigration process, trimmed my expenses, found a position that is frequently silly but tolerable for extended periods of time, and started looking for work before the new gig, mostly the same as the last gig, became unbearable. Everything other than the immigration process was burnout induced, so I can't claim that it was a clever strategy, but the net effect is that I kept sacrificing things at the altar of Being Okay With Less, and now I am in an apartment so small that I think I almost fractured my little toe banging it on the side of my bed frame, but I have the luxury of not lying.
If I had to write down what a potential exit pathway looks like, it might be: Find a job even if you must navigate the Vortex, and it doesn't matter if it's bad because there's a grace period where your brain is not soaking up the local brand of madness, i.e, when you don't even understand the local politics yet Meet good programmers that appreciate things like mindfulness in your local area - you're going to have to figure out how to do this one Repeat Step 1 and Step 2 on a loop, building yourself up as a person, engineer, and friend, until someone who knows you for you hires you based on your personality and values, rather than "I have seven years doing bullshit in React that clearly should have been ten raw HTML pages served off one Django server"
A CEO here told me that he asks people to self-evaluate their skill on a scale of 1 to 10, but he actually has solid measures. You're at 10 at Python if you're a core maintainer. 9 if you speak at major international conferences, etc. On that scale, I'm a 4, or maybe a 5 on my best day ever, and that's the sad truth. We'll get there one day.
I will always hate writing code that moves the overall product further from Quality. I'll write a basic feature and take shortcuts, but not the kind that we are going to build on top of, which is unattractive to employers because sacrificing the long-term health of a product is a big part of status laundering.
The only piece of software I've written that is unambiguously helpful is this dumb hack that I used to cut up episodes of the Glass Cannon Podcast into one minute segments so that my skip track button on my underwater headphones is now a janky fast forward one minute button. It took me like ten minutes to write, and is my greatest pride.
Have I actually worked with Google? My CV says so, but guess what, not quite! I worked on one project where the money came from Google, but we really had one call with one guy who said we were probably on track, which we definitely were not!
Did I salvage a A$1.2M project? Technically yes, but only because I forced the previous developer to actually give us his code before he quit! This is not replicable, and then the whole engineering team quit over a mandatory return to office, so the application never shipped!
Did I save a half million dollars in Snowflake expenses? CV says yes, reality says I can only repeat that trick if someone decided to set another pile of money on fire and hand me the fire extinguisher! Did I really receive departmental recognition for this? Yes, but only in that they gave me A$30 and a pat on the head and told me that a raise wasn't on the table.
Was I the most highly paid senior engineer at that company? Yes, but only because I had insider information that four people quit in the same week, and used that to negotiate a 20% raise over the next highest salary - the decision was based around executive KPIs, not my competence!
·ludic.mataroa.blog·
The Complex Problem Of Lying For Jobs — Ludicity
‘I Applied to 2,843 Roles’ With an AI-Powered Job Application Bot
‘I Applied to 2,843 Roles’ With an AI-Powered Job Application Bot
The sudden explosion in popularity of AI Hawk means that we now live in a world where people are using AI-generated resumes and cover letters to automatically apply for jobs, many of which will be reviewed by automated AI software (and where people are sometimes interviewed by AI), creating a bizarre loop where humans have essentially been removed from the job application and hiring process. Essentially, robots are writing cover letters for other robots to read, with uncertain effects for human beings who apply to jobs the old fashioned way.
“Many companies employ automated screening systems that are often limited and ineffective, excluding qualified candidates simply because their resumes lack specific keywords. These systems can overlook valuable talent who possess the necessary skills but do not use the right terms in their CVs,” he said. “This approach creates a more balanced ecosystem where AI not only facilitates selection by companies but also supports the candidacy of talent. By automating repetitive tasks and personalizing applications, AIHawk reduces the time and effort required from candidates, increasing their chances of being noticed by employers.”
AI Hawk was cofounded by Federico Elia, an Italian computer scientist who told 404 Media that one of the reasons he created the project was to “balance the use of artificial intelligence in the recruitment process” in order to (theoretically) re-level the playing field between companies who use AI HR software and the people who are applying for jobs.
our goal with AIHawk is to create a synergistic system in which AI enhances the entire recruitment process without creating a vicious cycle,” Elia said. “The AI in AIHawk is designed to improve the efficiency and personalization of applications, while the AI used by companies focuses on selecting the best talent. This complementary approach avoids the creation of a ‘Dead Internet loop’ and instead fosters more targeted and meaningful connections between job seekers and employers.”
There are many guides teaching human beings how to write ATS-friendly resumes, meaning we are already teaching a generation of job seekers how to tailor their cover letters to algorithmic decision makers.
·404media.co·
‘I Applied to 2,843 Roles’ With an AI-Powered Job Application Bot
Measuring Up
Measuring Up
What if getting a (design) job were human-centered?How might we reconsider this system of collecting a pool of resumes and dwindling them down to a few dozen potential candidates? With so many qualified individuals in the job market, from new grads to seasoned professionals, there has to be a fit somewhere.Call me an idealist — I am.In an ideal world, somehow the complexity of what makes a person unique could be captured and understood easily and quickly without any technological translators. But until then, a resume and a portfolio will have to do, in addition to the pre-screening interviews and design challenges. Without diving into a speculative design fiction, what if getting a (design) job were human-centered? How might the system be a bit more personal, yet still efficient enough to give the hundreds of qualified job seekers a chance in a span of weeks or months?
despite our human-centered mantra, the system of getting a job is anything but human-centered.For the sake of efficiency, consistency is key. Resumes should have some consistent nature to them so HR knows what the heck they’re looking at and the software can accurately pick out whose qualified. Even portfolios fall prey to these expectations for new grads and transitional job seekers. Go through enough examples of resumes and portfolios and they can begin to blur together. Yet, if I’m following a standard, how do I stand out when a lot of us are in the same boat?
·medium.com·
Measuring Up
the earnest ambitious kid's guide to investors
the earnest ambitious kid's guide to investors
  1. Fundraising is brain damage, so spend as little time doing it as possible
  2. Create an alter ego who you don for fundraising purposes
  3. Don’t spend a lot of time with VCs if you don’t need VC $
  4. Only talk to investors with decision-making power, preferably angels
  5. You know more about your business & domain than 90% of investors
  6. Momentum matters and sequencing is smart
  7. People don’t belong on pedestals
  8. Beware of intellectual dementors and clout demons
  9. People will help you if you ask for what you want clearly and concisely
VCs need to believe that your company could be a billion-dollar business and generally lack imagination — you need to paint a vivid picture of this path for them, starting with the striking protagonist character you play in your company’s story.Your alter ego should never lie, but it should be completely comfortable showing the fullest expression of your ambition to people who probably intimidate you. Fundraising is a snap judgment game — most VCs are trying to pattern-match you to a founder archetype who already won. They index primarily on IQ, self-belief, experience, and personability (in that order). A general rule of thumb is that to be taken seriously in SV, male founders would benefit from acting warmer, while female founders are taken more seriously when they act colder. Both benefit from acting a little entitled.
a VC’s job is to make a diversified portfolio of bets — you are only one. Most founders find being around VCs distracting and draining because they feel pressure to perform the role of ‘impressive person.’ If you can’t immediately capture value from your performance… why waste your energy?
don’t expect the average investor to provide much value beyond money and connections. This makes the 10% of investors who can be legitimately useful to your business worth their weight in gold. Develop litmus tests to identify the valuable ones quickly and avoid wasting your time trying to convince nonbelievers.
our goal here is to spend as little time fundraising as possible — which requires being strategic about the order in which you talk to investors and how you talk about where things stand as you progress through the raise. The combined force of controlling those two variables are what “generates momentum” during your fundraise process.
Make a list of all the investors you know and can get introduced to, ordering them by the ones you most want on board to the ones you couldn’t care less aboutTalk first to a few low-stakes investors at the bottom of your list to practice your pitch and identify common investor questions and critiques you’re going to getIf available to you, next get a few investors who already wanted to give you money on board so you have a dollar amount you can say you’ve raisedWork your way up your investor list, talking to the investors you most-want-on-board-but-still-need-to-convince last (this optimizes your odds they say yes)
This all goes by much faster if you court investors similarly to how hot girls treat their many potential suitors. If your raise is already a little taken and you exude an air that you don’t need them, mimetically-minded investors become much more interested.
If you’re anything like me, you will worry intensely about not making a fool of yourself. It will probably go ok, but not as amazing or illuminating as you’d hoped. You might leave and feel a deep sense of lostness set in. This is all very normal. In time you will see them in increasing clarity, often noticing the differences between your and their values and why you would not enjoy living their life at all.
the people on pedestals probably hate being there. It’s lonely, hard to trust that the intentions of the new people around you are pure, and you often feel like you’re constantly letting people down. In the end, idolization hurts everyone involved.
Beware of intellectual dementors and clout demonsIntellectual dementors will try to eat your ideas and interestingness — not necessarily to copy you, but to wring your brain dry to amass knowledge themselves. They often play mini IQ games/tests of will in conversation and masquerade as investors while never actually investing. Clout demons are similar, but view people less as brains and more as stepping stones towards supreme social status. The power move to protect yourself from both is to simply abstain from playing their games — give as little info on yourself and your ideas as possible and reflect their questions directly back at them.
People will help you if you ask for what you want clearly and concisely
Knowing what you want requires a lot of upfront soul-searching, followed by strategic and long-term thinking once you’ve committed to a thing (I can’t really demystify this more). Once you’re all in, I highly recommend diligently keeping a list somewhere of the top three things you currently need help with so when people ask, you’re ready.
You don’t want to make people feel like you’re using them but you do want to use your social capital for things you care about. General rule of thumb: ask for things either 1) after a positive interaction or 2) completely out of the blue with a concisely written and compelling email/text. Tone matters because you don’t want to sound desperate and you do want to show you know how to play the game (write like the founder you most admire talks).
once we’ve taken action on behalf of something, our brain assigns more value to said thing. Tim Keller: “The feeling of love follows the action of love.” Love is a strong word here, but the point stands — help people help you. Startups are long-term games, so it only makes sense to do them with people you truly want to be around for a very long time.
·mothfund.substack.com·
the earnest ambitious kid's guide to investors
Muse retrospective by Adam Wiggins
Muse retrospective by Adam Wiggins
  • Wiggins focused on storytelling and brand-building for Muse, achieving early success with an email newsletter, which helped engage potential users and refine the product's value proposition.
  • Muse aspired to a "small giants" business model, emphasizing quality, autonomy, and a healthy work environment over rapid growth. They sought to avoid additional funding rounds by charging a prosumer price early on.
  • Short demo videos on Twitter showcasing the app in action proved to be the most effective method for attracting new users.
Muse as a brand and a product represented something aspirational. People want to be deeper thinkers, to be more strategic, and to use cool, status-quo challenging software made by small passionate teams. These kinds of aspirations are easier to indulge in times of plenty. But once you're getting laid off from your high-paying tech job, or struggling to raise your next financing round, or scrambling to protect your kids' college fund from runaway inflation and uncertain markets... I guess you don't have time to be excited about cool demos on Twitter and thoughtful podcasts on product design.
I’d speculate that another factor is the half-life of cool new productivity software. Evernote, Slack, Notion, Roam, Craft, and many others seem to get pretty far on community excitement for their first few years. After that, I think you have to be left with software that serves a deep and hard-to-replace purpose in people’s lives. Muse got there for a few thousand people, but the economics of prosumer software means that just isn’t enough. You need tens of thousands, hundreds of thousands, to make the cost of development sustainable.
We envisioned Muse as the perfect combination of the freeform elements of a whiteboard, the structured text-heavy style of Notion or Google Docs, and the sense of place you get from a “virtual office” ala group chat. As a way to asynchronously trade ideas and inspiration, sketch out project ideas, and explore possibilities, the multiplayer Muse experience is, in my honest opinion, unparalleled for small creative teams working remotely.
But friction began almost immediately. The team lead or organizer was usually the one bringing Muse to the team, and they were already a fan of its approach. But the other team members are generally a little annoyed to have to learn any new tool, and Muse’s steeper learning curve only made that worse. Those team members would push the problem back to the team lead, treating them as customer support (rather than contacting us directly for help). The team lead often felt like too much of the burden of pushing Muse adoption was on their shoulders. This was in addition to the obvious product gaps, like: no support for the web or Windows; minimal or no integration with other key tools like Notion and Google Docs; and no permissions or support for multiple workspaces. Had we raised $10M back during the cash party of 2020–2021, we could have hired the 15+ person team that would have been necessary to build all of that. But with only seven people (we had added two more people to the team in 2021–2022), it just wasn’t feasible.
We neither focused on a particular vertical (academics, designers, authors...) or a narrow use case (PDF reading/annotation, collaborative whiteboarding, design sketching...). That meant we were always spread pretty thin in terms of feature development, and marketing was difficult even over and above the problem of explaining canvas software and digital thinking tools.
being general-purpose was in its blood from birth. Part of it was maker's hubris: don't we always dream of general-purpose tools that will be everything to everyone? And part of it was that it's truly the case that Muse excels at the ability to combine together so many different related knowledge tasks and media types into a single, minimal, powerful canvas. Not sure what I would do differently here, even with the benefit of hindsight.
Muse built a lot of its reputation on being principled, but we were maybe too cautious to do the mercenary things that help you succeed. A good example here is asking users for ratings; I felt like this was not to user benefit and distracting when the user is trying to use your app. Our App Store rating was on the low side (~3.9 stars) for most of our existence. When we finally added the standard prompt-for-rating dialog, it instantly shot up to ~4.7 stars. This was a small example of being too principled about doing good for the user, and not thinking about what would benefit our business.
Growing the team slowly was a delight. At several previous ventures, I've onboard people in the hiring-is-job-one environment of a growth startup. At Muse, we started with three founders and then hired roughly one person per year. This was absolutely fantastic for being able to really take our time to find the perfect person for the role, and then for that person to have tons of time to onboard and find their footing on the team before anyone new showed up. The resulting team was the best I've ever worked on, with minimal deadweight or emotional baggage.
ultimately your product does have to have some web presence. My biggest regret is not building a simple share-to-web function early on, which could have created some virality and a great deal of utility for users as well.
In terms of development speed, quality of the resulting product, hardware integration, and a million other things: native app development wins.
After decades working in product development, being on the marketing/brand/growth/storytelling side was a huge personal challenge for me. But I feel like I managed to grow into the role and find my own approach (podcasting, demo videos, etc) to create a beacon to attract potential customers to our product.
when it comes time for an individual or a team to sit down and sketch out the beginnings of a new business, a new book, a new piece of art—this almost never happens at a computer. Or if it does, it’s a cobbled-together collection of tools like Google Docs and Zoom which aren’t really made for this critical part of the creative lifecycle.
any given business will find a small number of highly-effective channels, and the rest don't matter. For Heroku, that was attending developer conferences and getting blog posts on Hacker News. For another business it might be YouTube influencer sponsorships and print ads in a niche magazine. So I set about systematically testing many channels.
·adamwiggins.com·
Muse retrospective by Adam Wiggins
Snapchat, The Browser Company, and picking winning founders with Ellis Hamburger
Snapchat, The Browser Company, and picking winning founders with Ellis Hamburger
Is the founder focused on a market opportunity, or a way that they want to change and improve our daily lives? It’s the difference between pitching the tool vs. the benefit. The best founders are always focused on the benefit—they’re putting themselves in the shoes of the consumer, instead of just building something because they can.
On how to identify a winning founder: “Great, thoughtful design. Great design tells you if the founder is focused, has good taste, understands the simplicity required to connect with the average consumer, and has a strong, specific point of view on what they’re building. It has always been my barometer. Great design is harder to identify than it sounds, though.”
·joinprospect.com·
Snapchat, The Browser Company, and picking winning founders with Ellis Hamburger
tech interviewing is broken | basement community
tech interviewing is broken | basement community
i don't even really care if the answer is right, as long as the person i'm talking to can talk about complexity cogently. if i'm interviewing for an entry-level position, i don't even really care about that, we can teach it, it's not that hard.
Anecdotally I have noticed junior engineers being increasingly difficult to work with since many of them are leetcode drones who have issues working and figuring things out on their own. They got really good at passing 'the test' but did not develop many other skills relating to technology and many times do not really have an outside interest in it beyond being able to get a job.
·basementcommunity.com·
tech interviewing is broken | basement community
tech interviewing is so incredibly fucked
tech interviewing is so incredibly fucked
in the article they're talking about how live-coding is inherently harder for people who have been working in the industry longer. which sounds.....not right? like why would more experience with coding make you worse at interviewing? it's because these interviews filter for people who spend their free time practicing coding prompts and algorithms for fun. and people who work 9-5 jobs and have lives outside of work just don't do that, so they're inherently going to be worse at these type of interviews.
·basementcommunity.bearblog.dev·
tech interviewing is so incredibly fucked