61–70 of 119 posts
https://www.ozchen.com/fuck-balance/
https://www.ozchen.com/hanlons-razor/
https://www.ozchen.com/what-is-content-strategy-definition/
To my own surprise, it was through writing that I landed gigs in UX, UI and content strategy, and now parlayed into a full time content strategy job.
http://www.electricstuff.co.uk/ http://omeganaught.com/ http://krazerlasers.com/ http://www.etotheipiplusone.net/
I tried to get all the important details on a single page and isolate the tech jargon to appeal to non-technical clients. I personally found and had non-technical friends agree with me that a lot of developer portfolios focused too much on the tech (e.g. "I'm a Node developer who loves React!") or go into too much detail about project specifics so I tried to avoid that.
Very clear technical writing, mostly about web technologies.
https://brandur.org/articles Very clear technical writing, mostly about web technologies.
At the risk of sounding pompous. I really like my portfolio site: [link redacted] Why? I built it for myself. Not for what I thought recruiters/employers wanted to see. I simply wanted a place to collect some of the projects I work on. And more importantly one that captured my personality a bit. It's not perfect, I look at it and see a ton things I'd refactor. But it get's people to laugh or start a conversation abou…
As a non-coder it feels like the learning curve for building a website portfolio is super high - even though I am told by coders that it is not. Could anyone lend some guidance on where to start?