Thomas Kjeldahl Nilsson retweeted
I ❤️ this aspect of being an indie contractor/consultant:
When I need downtime I just have a quick chat with my client.
"I'll be away [...] Just making sure it doesn't create any issues for you. No? Ok good." Then I take the time off.
You should have clients, not bosses. 🙂
Thomas Kjeldahl Nilsson retweeted
Here's one very specific thing I really like about working as a freelancer/contractor:
One hour of work == one hour billed/compensated. 🤝
As a salaried employee with a fixed annual salary, compensation per unit of time worked can be way, way more unclear. 😄
Thomas Kjeldahl Nilsson retweeted
For new developers: you *don't* have to be a genius to do well. A decent sense of pride in your craft, ability to work well with others, mastery of a basic skillset, and ability to get work done consistently == more valuable than a flaky rockstar/ninja to most employers. :)
Thomas Kjeldahl Nilsson retweeted
Here's one way to look for contracting/consulting leads:
Get in touch with local software dev agencies.
The successful ones are overbooked/understaffed regularly, which means they may need subcontractors to help out....
This is where you come in (if they have met you) 💪
Thomas Kjeldahl Nilsson retweeted
A few ways to make your way life simpler as a freelancer 😎
- Earmark taxes (VAT etc) into a separate account
- Have written standard operating procedures (README for your biz!)
- Pay/tag/archive invoices as they show up—not way down the line!
- Work with a good accountant 📊
Thomas Kjeldahl Nilsson retweeted
Bit of warning: Impostor syndrome can feel even worse when you're an independent dev 💀
"They'll find me out and drop my engagement!"—still an irrational fear for me after 20 years as a dev & 7 years as a contractor/consultant (w/ happy clients).
Just keep going anyway! 🌄
Thomas Kjeldahl Nilsson retweeted
"I'm afraid I won't find any clients, because I'm not a hotshot dev."
Relax! You really don't have to be a top 5% rockstar developer.
You just have to be decently competent, reliable and easy to work with. 🙂
Thomas Kjeldahl Nilsson retweeted
Sometimes it takes a while from when you think about doing something... until you actually follow through on it.
Example: my slow, winding path to freelance/contract work... 😆
👇
Thomas Kjeldahl Nilsson retweeted
Sometimes you have to plant new seeds 🌱, other times you harvest 🚜
How much time do you spend on learning and building things on your own vs doing work for others (employer or client?)
When you're working for yourself, you decide! Per week, month, year. 📆
Thomas Kjeldahl Nilsson retweeted
Runway is everything. Build up your buffer as soon as you can! 🪙
6-12 months of modest salary in your company bank account is not just for emergencies:
When you know that you can afford to walk away, you'll be way more confident and relaxed around prospects and clients. 👍
Thomas Kjeldahl Nilsson retweeted
As a software developer, it's common to experience imposter syndrome – that nagging feeling of inadequacy and self-doubt
Overcoming imposter syndrome can be a challenge, living with it is what I've learned to do
Here's how:
Thomas Kjeldahl Nilsson retweeted
In an effort to look smart, some engineers think they have to make others feel dumb
Then they wonder why they have a hard time convincing others of their opinions
Being right doesn't matter if you don't know how to talk to people properly
Thomas Kjeldahl Nilsson retweeted
Supporting another developers success will literally never ruin yours.
Thomas Kjeldahl Nilsson retweeted
I'm not against VC in general, but I do think that its incentives are misaligned with giving people long term ownership over their data
in pursuit of hyper-growth, Evernote subsidized pricing and hired aggressively — but eventually they had to become profitable, and lock-in is the quickest path
"File over app" has to be baked into the product itself, irreversibly. This is also why Obsidian is 100% user-supported, profitable, and not trying to grow beyond its means
nitter.gq/kepano/status/16…
File over app
File over app is a philosophy: if you want to create digital artifacts that last, they must be files you can control, in formats that are easy to retrieve and read. Use tools that give you this freedom.
File over app is an appeal to tool makers: accept that all software is ephemeral, and give people ownership over their data.
In the fullness of time, the files you create are more important than the tools you use to create them. Apps are ephemeral, but your files have a chance to last.
The pyramids of Egypt contain hieroglyphs that were chiseled in stone thousands of years ago. The ideas hieroglyphs convey are more important than the type of chisel that was used to carve them.
The world is filled with ideas from generations past, transmitted through many mediums, from clay tablets to manuscripts, paintings, sculptures, and tapestries. These artifacts are objects that you can touch, hold, own, store, preserve, and look at. To read something written on paper all you need is eyeballs.
Today, we are creating innumerable digital artifacts, but most of these artifacts are out of our control. They are stored on servers, in databases, gated behind an internet connection, and login to a cloud service. Even the files on your hard drive use proprietary formats that make them incompatible with older systems.
Paraphrasing something I wrote recently:
> If you want your writing to still be readable on a computer from the 2060s or 2160s, it’s important that your notes can be read on a computer from the 1960s.
You should want the files you create to be durable, not only for posterity, but also for your future self. You never know when you might want to go back to something you created years or decades ago. Don’t lock your data into a format you can’t retrieve.
These days I write using an app I help make called Obsidian (@obsdmd), but it’s a delusion to think it will last forever. The app will eventually become obsolete. It’s the plain text files I create that are designed to last. Who knows if anyone will want to read them besides me, but future me is enough of an audience to make it worthwhile.
Thomas Kjeldahl Nilsson retweeted
artists are starting to take action to protect their own art from AI by "poisoning" it w. glaze
then these AI prompters have the gall to say "you're ruining our training data"
like,
1. yes
2. it's not yours you entitled prick
3. calling art "training data" says a lot about you
Thomas Kjeldahl Nilsson retweeted
I've had this book in me for years, and I finally wrote it! Just the ISBN missing now.

ALT A book cover in the style of Steve Krug's design classic "Don't make me think". In place of the author name, it says "Seriously, Dude". Below it, a small graphic of a gray-haired woman pulling her glasses down to look at you. Book title is "Don't make me squint". Below the title, the text "Ditch the tiny fonts, poor contrasts, and incomprehensible icons. That's it. That's the book."
Thomas Kjeldahl Nilsson retweeted
It’s tempting to think that hard problems require complex code.
I’d like to argue that the opposite is true: the harder the business problem, the more we need to invest in making the solution as easy as possible to understand for people versed in the domain.
Thomas Kjeldahl Nilsson retweeted
listen, it's just a little difficult to take seriously some of these VCs and execs who are panicking about SVB under the guise of being worried about the employees and the little guys

















![Text messages leaked from discovery in the Elon Musk lawsuit. Highlighted are text messages from Jason Calacanis to Musk, reading "Day zero. Sharpen your blades boys [knife emoji]. 2 day a week Office requirement = 20% voluntary departures"](https://pbs.twimg.com/media/FrCKouTWwAA8uef.jpg?name=small&format=webp)