Donovan Adams

So many things to unpack in the wake of another company squeezing their open source users towards licensing. Thinking of the current OSS climate and the lack of participation of companies generally as well as not being able to endorse using a solution fearing that a company will pull the rug out from under you once you're fully integrated with a solution. https://lnkd.in/gVpME4Uz

2

1 Comment

Pro tip for graphic designers working on conference T-shirts: check which parts of your design are covered by the conference lanyard. This tip brought to you by Udemy’s subversive “AWS kills for all” messaging.

35

3 Comments

I know lots of people are wondering about what the cookie preference UX in Google Chrome will end up looking like—this is a different but related question from a web development point of view. Technically, how would Google Chrome make a "cookie" option that covers both conventional cookies and Google's own user tracking done with non-cookie technologies? (Obviously, one setting has to control both—otherwise the cookies off option would be more like a "take all the ad money from independent sites and send it to YouTube lol" button that no regulator would let them get away with) It looks doable in a few different ways. Thinking about simplicity and privacy though. * Third-party cookie check on Google sites. When a user visits a Google site, the site would use a cookie on a dedicated test domain to see if third-party cookies work. If the browser blocks a third-party cookie, also block Google ad personalization. Least work on the browser side. * Bundle the "cookies off" preference in the browser with Global Privacy Control (GPC). Then, Google sites can check GPC and not do personalized ads if it's on. * Extend the existing browser feature detection mechanism to enable Google Chrome to communicate to Google web properties if it has third-party cookies turned on. ( https://lnkd.in/gyiMqd5k ) Any of these would be fairly straightforward to implement in a predictable amount of development time. Any others?

5

Project update! My application tracking extension is now doing fuzzier matching and injecting new information into LinkedIn (and other sites) to keep me from doubling up on applications. Next up: local storage and bulk import/export operations...

12

2 Comments

Make an indoor map and embed it on your website in seconds. It really is this easy with Mappedin.

24

Stories from the Trenches: What I’ve learned from Working as a Blind Developer for a Sighted Dev Team https://buff.ly/3ZrUbQT #Disabiity #Blind #WebDev #WebDevelopment #DigitalAccessibility #Accessibility #A11y

1

If you use mid journey there is. Web interface now #genai. This article breaks its down

4

Sinek dropped this shockingly concise description of building trust in a recent interview/discussion with Trevor Noah (https://lnkd.in/erv2VhBG), and it was so good I was left scrambling to type it into my phone so I would remember it. How often do you ask for help? Managers want their employees to ask for help when they need it - how often are you demonstrating that skill and being meaningfully open to getting help when you need it?

3

The bigger my team and tech-stack grows, the more I try to identify and improve our curation of Internal Libraries. To.. 🌅 Efficiently and effectively spread the expertise of our devs 💡 Keep development intuitive for smooth cross-pollinating collab 🔐 Protect proprietary algorithms in a dynamic codebase 🛫 Boost code velocity Read more - https://lnkd.in/g86jb2yy Thoughts?! #softwareengineering #code

30

𝗟𝗲𝘀𝘀𝗼𝗻𝘀 𝗳𝗿𝗼𝗺 𝗦𝘁𝗲𝘃𝗲 𝗝𝗼𝗯𝘀: 𝗧𝗵𝗲 𝗣𝗼𝘄𝗲𝗿 𝗼𝗳 𝗗𝗲𝘁𝗮𝗶𝗹𝘀 𝗮𝗻𝗱 𝗜𝗻𝘁𝗲𝗴𝗿𝗮𝘁𝗲𝗱 𝗘𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲𝘀  The 𝘚𝘵𝘦𝘷𝘦 𝘑𝘰𝘣𝘴 biography by Walter Isaacson highlights how transformative a dedication to detail can be in building iconic products. Jobs was relentless about the small things – the often-overlooked details he believed were essential to a product’s soul. Take, for instance, his insistence on a slot-loading CD/DVD drive for the iMac instead of the traditional tray. For Jobs, this wasn’t just an aesthetic choice but a statement of simplicity and elegance. He felt users would sense this refinement, even unconsciously. It’s a reminder that what might seem minor can ultimately shape a product’s perception and feel. This meticulous attention extended across everything Apple created. Jobs was known to care about typefaces, button layouts, and even the arrangement of circuit boards inside devices, setting a standard that every touchpoint should be crafted with care and intention. In software, he pushed for fluid animations and subtle sounds that felt intuitive, creating harmony between user and product. But his focus wasn’t only on the details – he believed in building fully integrated experiences. Apple’s software ecosystem is a perfect example. Consider how iMessage, FaceTime, and AirDrop work seamlessly across devices. This seamless integration wasn’t accidental; it was a result of careful planning where every piece was designed to complement the others, allowing users to switch effortlessly between devices. Another example is iCloud, which connects photos, documents, and apps across devices in real-time, giving users a sense of continuity and connection. For software and digital products, these principles are powerful. Imagine creating an experience that doesn’t just optimize each part but feels unified end-to-end. Integrating design and functionality seamlessly – from backend processes to front-end interfaces and customer support – can turn a functional product into a memorable one. And paying close attention to the details, like smooth transitions or well-paced loading speeds, often makes the difference between a good experience and a great one. Jobs’ approach reminds us that a product’s magic often lies in the fine details and the effort to build an experience that feels complete, connected, and crafted with intention. #ProductDesign #CraftingExperiences #LeadershipLessons

4

2 Comments

We have seen some interesting anecdotes with clients for Google's AI Overviews, we can't call them "trends" yet, but we intend to run an analysis to validate these across thousands of terms. Alisa Scharf is sharing her early take / spidey senses on where she's seeing this go. Looking forward to digging in deeper in a month or so and validating these deeper. Classifying query type (how to vs deep how to vs what is, branded, non branded, etc) could be the direction this got me thinking in, what clusters fit into what impact level, so you can help your company prepare for where there's upside and downside potential. https://lnkd.in/e6Zk7wd2

38

9 Comments

Following the Pareto principle 80% of the outcome can be achieved by applying 20% of the effort. And if a new product or feature is being built typically the remaining >=20% of the outcome (usually more than that) will not be needed at all or something altogether different will be required as more is gradually discovered after the first release. Defining the scope wisely and iteratively improving on the first version is key to improved speed, quality and reduced costs. Also feedback will be received much faster and learning will happen earlier. In comparison in the classical waterfall model scope is fixed, delivery is late, costs are exceeded, quality suffers under the time pressure to follow the plan and feedback after the release is either received too late or ignored altogether. The result is wasted effort and less value delivered. It comes down to working smart, delivering often, producing value and learning fast from the users vs following the plan, being late, overrunning budget, ignoring feedback and producing hard to use or useless software #extremeprogramming #agile #productmanagement #softwaredevelopment #paretoprinciple #waterfall

1

Question for executives: if at the snap of your fingers your entire organization could embody the lessons of a single book, what book would that be?

6

2 Comments

tldr: I'm hiring! As many of you know, I recently joined Lattice as their SVP of Engineering and I'm excited to announce that I'm hiring for all Engineering levels and more broadly, Lattice has open roles across EPD. If you're wondering, why Lattice? The last few years have seen a step change in how we think about the meaning of work and the employer <> employee relationship - add on the fuel of AI taking our jobs and you could be forgiven for thinking the future of work looks bleak for employees. It doesn't need to be that way - here at Lattice we're building the next generation of talent tools to give employers insights and employees purpose because people matter at work. Among other things, we're using generative AI to securely analyze enormous volumes of data to unlock career insights faster and investing in building equitable feedback, compensation and employer analytics tools - not just for one company but for all companies. If you're interested in making a difference to the future of work then let's chat - all roles are remote eligible and based in the US. We have physical offices in San Francisco and NYC if you prefer the in-office environment.

324

48 Comments

Dash for Business

19

"To help preserve a safe Internet for content creators, we’ve just launched a brand new “easy button” to block all AI bots. It’s available for all customers, including those on our free tier." This is really neat! Whatever you land on AI scraping, giving site owners the one-click ability to make a choice is great. Some will choose not to use this; others will hit the button. Making it this easy means it's a choice about the principles, not any kind of technical considerations. Which is what it should be. Not every site is on Cloudflare (and some also choose not to use it because of how it's historically dealt with white supremacist / Nazi content). But many are, and this makes it easy for them. Other, similar providers will likely follow quickly.

3