Dan Spratling

@danspratling.dev

Technical Lead • Product Engineer • Ex-Founder • UX/DX/A11y • Jamstack Nerd • NextJS/React/Astro

So just had a technical test that expected me to understand, and make changes to, a python API. This is for a Frontend developer role where I was very upfront that I lean more towards design and have no experience with python 🙃

It absolutely sucks that specialising in, and being great at, frontend development - understanding designs, design systems, APIs and the overlap into backend that every frontend framework now requires more than every - somehow isn't enough Yet backend being awful at implementing design is fine

Kyle Shevlin (he/him)@kyleshevl.in · 2y ago

A bit of unsolicited advice to devs earlier in their career: While I love frontend and genuinely think it's crucial to company success, IME, companies discount frontend expertise. Gobble up what backend experience you can early in your career. Think it'll keep more doors open to you.

One thing I'm seeing more and more as I'm job hunting Engineering manager roles managing a full-stack team that require significant backend experience and zero frontend experience Frontend development isn't a secondary skill, it's equally as nuanced as backend Let's start treating them equally 👏

Here's something that really grinds my gears in the UX of the web In what possible world am I meant to know which of these options is the right login. Why would I need 9 different options for a login? Let me log in and find my way to what I want to do afterwards

A screenshot of BrightPay's login window, with 9 different links to various login pages. All with poorly branded names that don't easily highlight their functionality.

As usual, Danny hits the nail on the head. 🔨 I’ve had to fight this temptation myself. Cursor changes 50 lines and the lazy part of my brain says "I’m sure it’s fine, just accept the changes". Seems like a great way to plateau in your growth as a developer. 😬

Danny Thompson@dthompsondev.bsky.social · 2y ago

Tutorials used to create tutorial hell, but I feel like after quite a few recent conversations, there is a new "hell" for beginners. ChatGPT Hell. I am meeting so many beginners that rely on ChatGPT to deliver all of the code and answers but they do not know what is going:

I've not written a resume in 5 years (or CV for us Brits) Even having 10 years of experience, it's really hard to get it to a good enough point where it shows what I can do well Squeezing each role into a few lines & building excitement is difficult And that's only one part of job-hunting!

I see so much FUD about the future of sw engineering, mostly from non-devs. Along the lines of “soon anyone can spin off AI agents in bulk that act as hundreds of devs.” A false premise. Just open your airline app that is built by ~hundreds of devs over 10+ years

My portfolio's been neglected for way too long So while looking for new work, I'm also flexing my design skills and bringing my portfolio up to date. Everyone good with yellow?

Homepage hero with the content "Dan Spratling, UX Engineer, Frontend Developer, Technical Lead" with the name in oversized, bright yellow lettering and the subtitle sitting in the gap to the right of Dan. Below is a masonry grid of projects created by Dan and in the center of this project grid is an image of Dan sitting at a table smiling towards the camera.

figured may as well repost it here seein' as others elsewhere are reposting the implementation as theirs 💀 updated to include the <input> reveal 🤙 and if you like this sort of thing, sign up for "The Craft of UI", where we break down things like this craftofui.substack.com

The Craft of UI | Jhey ʕ•ᴥ•ʔ | Substack

Showing you how to bring ideas to life with code 🤙. Click to read The Craft of UI, by Jhey ʕ•ᴥ•ʔ, a Substack publication.

craftofui.substack.com

I've been looking for work for the past few weeks What's most interesting is that applying is genuinely exciting After working for myself for the past 4 years, that feels strange I think it's due to gaining the confidence to apply at companies I'd never believed I could work at before

Someone mentioned me in a comment where they are debating whether or not the top 10 Fortune 500 companies use Agile (as in, some methodology based on the Agile Manifesto). My thoughts on this: worry about being nimble, not about Agile (TM). That's what the best orgs do, anyway.

As the author of the article, a few raw thoughts:

1. It's more important that a team/company solve for *their own, specific* pain points, and to operate using their own strengths (and within their own constraints), than to follow any frameworks, however popular or well-known that framework is.

2. Different companies have different strengths and constraints. Something we talk very little about is how the top of the market tends to compensate much better: and thus hires people of whom they can expect more: more self-starter attitude, more autonomy, more "thinking outside the box." They also line up outsized rewards around all of this! See https://blog.pragmaticengineer.com/software-engineering-salaries-in-the-netherlands-and-europe/

3. Sketching out a plan before starting, Scrum, Kanban, TDD, XP: these are all tools that any one team can use. The best teams have a broad set of tools and use whatever makes most sense for their context.

4. The Agile Manifesto is 22 years old. A lot has

Today is my day off But I love coding, and I love building Skyward, so I often end up working in my time off So, instead of fighting with myself about it, I set a few rules 1. Work on what I want (not client work) 2. Stop when I want 3. Try and be somewhere different

Bild

My end goal is financial security/resiliency Enough money that me and my family can be happy with minimal risk if something were to go wrong Similar to early retirement, but I really enjoy what I do so unless I burn myself out, I think I'd want to keep going once I reach my goal 😅

Post nicht verfügbar.