Means & Methods is now live on https://t.co/51EnluPYHn.
A collection of practical techniques to achieve excellence in interface design, covering 100+ topics across 11 chapters, with plenty of interactive examples and code.
New members welcome; enjoy!
🚀It's been an exciting 2 days since launch!
- 250+ users signed up
- 240+ stories completed
- we even had our first free trial -> paid conversion!
The best part has been seeing all the fun, AI-generated stories being created that are based on the children's interests! 😍
📦 Every interface design element is a rectangular box.
Icons? A box
Buttons? A box
Headlines? A box
Form labels? A box
Negative space? Most definitely, a box
If you don't already... using the box model will drastically improve the way you design.
Here's why...
I’m looking forward to diving into a new project at the start of next year and am searching for one that will be a good fit. I’ll have 20 hours per week to devote to this. Please share the word and if you know of a project that might be a good fit, I’d love to connect. Thanks!
Efficient context switching is a skill commonly overlooked by many software developers. Those small blocks of time in your schedule really add up. Using them effectively delivers significant productivity wins. Below are three techniques I find particularly valuable in this area.
No AB tests, no growth tactics, no hashtags, no marketing department, no cartoon characters on ladders.
Just trying to explain the product in clear terms with good taste and design https://t.co/Gc1D3vo5Zp
Design is hard.
But I’ve come to realize that laying out texts properly is 80% of what makes something look clean, and is the easiest thing you can do to make your design much nicer and more usable.
Here are 10 practical tips for improving your text layout.
I keep hearing that @GitHubCopilot is a particularly valuable tool for experienced engineers (not just new programmers). Does anyone have personal experience for/against this? I plan to try it out for a month across a number of projects/languages/etc and will share my findings.
@hstrowd@GitHubCopilot I used @GitHubCopilot for a few weeks. Super helpful for boilerplate code, plus common and/or repeatable methods. I think where it trips up less experienced folks is when it suggests something that "looks" like it should work but actually does not. Worth checking out though!
Designers often misunderstand the level of domain experience founders and exec teams have. They might not be doing what we’d consider “good research”, but they’ve often been talking to customers and bathing in the problem space for a considerable time.
Been playing around with #Ruby fibers to resolve a flakey test case covering some DB row locking functionality and they're honestly really cool. Ok, maybe not Friday night "cool", but definitely cool enough for a bored Wednesday evening.
Recently started listening to and commenting on music in realtime with my teammates. It's a great informal team building mechanism. I've learned a ton that I would never have thought to ask otherwise. Have any similar tips for this type of informal collaboration/team building?
Teambuilding alternative to Marginal: digital trustfalls. Run a script to erase your hard drive on a delay; have one of your coworkers connect remotely to your machine and stop the script before it executes.
Great question in this weeks @doist Async Newsletter: https://t.co/7k2P7oAQiu. Weekly book clubs have been a really fun and productive way for remote teams to feel more connected with your co-workers.
Had a good conversation with a client working on a Ruby app about when to include ! as a suffix on a method and when to avoid it. What guidelines do you use to influence/determine when it’s appropriate and when it’s unnecessary or confusing?
We've gained so much by using open source software while building @tuple.
As a small token of our appreciation, we're sending 3 OSS devs (and their +1s) on vacation!
Please help us find the most deserving folks by nominating/voting.
https://t.co/JC9FeKGRle