👾 Aaron Cordova

NEW: Internal Threads Internal threads allow you to spin up conversations in Slack from Pylon. It's great when you want to start a conversation with someone, but they primarily use Slack (e.g. engineers, product people or anyone who isn't living out of the support system). Common internal threads we are creating at Pylon: 1/ #bugs to report a potential bug 2/ #project channels to ask a team a question about a specific feature 3/ #feedback to report product feedback to the team It's been one of the most game-changing features we've released and we're so excited to share it with everyone. Enjoy!

44

3 Comments

One common question I get is, "What do you do as a Developer Advocate?" or "What does the Developer Experience team do?" (Even within Sendbird, haha 😂) The answer varies because the role of a Developer Advocate differs across companies. But I can clearly share what we do at Sendbird! And one great way to show this is by highlighting what we've accomplished!! Here's a recap of what we've done over the last three months. Huge thanks to the team! 🙌 (Jane Lee Katherine Na Yeon Kim Mansoo Kim Sunghyuk Kim Mickey C.) ======= 🚀 Dogfooding Session: We conducted an internal session for Sendbird Business Messaging, simulating a customer use case to improve our onboarding experience. 🎥 YouTube Videos: Released 5 videos covering AI Chatbot features to help users get started quickly. 📝 Feedback Channel: Actively collected and addressed feedback to enhance our documentation. 🤖 Interactive Demos: Built targeted demos for AI Chatbot in E-commerce, Healthcare, and Online Banking. 📚 Documentation Revamp: Improved our "Getting Started" guides, resulting in increased user engagement. For the full story, check out my Medium post: https://lnkd.in/gt-HGnER Looking forward to what we'll achieve next! 🙌 And one thing more, we're hiring a Technical Writer(https://lnkd.in/gFM4R9Wh), Please feel free to contact me if you are interested in this role! Also, if you're interested in becoming a Developer Advocate, don't hesitate to reach out!

53

2 Comments

I once asked a lead engineer on Angular: Which is better: Angular or React? His response: "Both require good engineering to be effective." So, my developer friends, consider this a reminder that "frameworks" like Diátaxis are fine, but they still require good engineering--such as UX, information architecture, style, maintenance processes, and so on--to create great documentation experiences for your customers. Alas, the framework alone isn't enough.

35

7 Comments

Three reasons I love doing DEFTs! We just wrapped up another DEFT for another great client. What's a DEFT you ask? It's our "Developer Experience Friction Audit Tool". Put simply, it's a holistic evaluation of your #DX / developer journey, from the perspective of your potential developer customer. Here's three reasons why I love performing DEFTS for our clients: 1. I get to meet great people who really care about their organization's developer journey / developer experience. 2. From new technologies and APIs, to frameworks and new types of learning resources, I get to learn new things all the time. Each project not only broadens my scope of experience, but allows me to see what's driving the pulse behind today's top companies and technologies. 3. DX audits are a chance to make a real difference for our clients and their developers. From identifying what's working, to areas of opportunity, it's rewarding when we uncover things our client's may have never thought about before. Want to learn more about DEFTs? Check out: https://lnkd.in/g3tNEneu

4

3 Comments

There were other examples of this around the web, but none explained _how_ automatic reloading worked in Django. Some implementations felt half-baked. I think this one stands apart. This is also my 70th blog post on DEV 😮 https://lnkd.in/gtC6sBMr

3

2 Comments

So this week, I learned about OpenGraph, modern web metadata standards, and integrating that, so YapperJobs now has social media previews! https://lnkd.in/e5fgf_DT If you're looking to learn more about OpenGraph, check out this page: https://lnkd.in/eQP4-NEv #sideprojects #openweb

5

1 Comment

Well it finally happened, kids. Playwright has surpassed Cypress.io in weekly downloads. What does it mean? A lot of things. We’ll be taking a look at this with Jonathan Canales on a livestream this Thursday, so tune in to get notified -> https://lnkd.in/eUS-2KCS We’ll take a look at the past, present and the future of end-to-end test automation and I can already tell it will be a juicy one 🙂 So what do you think are the impacts? When will Playwright’s growth slow down? Will Cypress surpass Playwright in the future?

1,012

82 Comments

Some unconnected thoughts on this “ghost developers” panic: Despite tech being a major economic driver for a couple of decades, MBA programs, and therefore the state of management thinking, are rooted in manufacturing. The mindless drive for efficiency in all kinds of businesses makes the most sense if you’re talking about factories and logistics. Not so much for knowledge work. Software is the only huge field where “R&D”, “production” and “services” are collapsed into one big undifferentiated mass. The output of product development is code shipped to production, and it needs to be continually maintained and updated. The closest thing software has to a manufacturing model is offshoring engineering to eg India or Eastern Europe, while keeping design and product/eng leadership in the US, but that creates ongoing problems because you can’t just hand off specs to India for manufacturing and move onto the next launch. Offshore teams need ongoing support because the customers need ongoing product support. Because engineers produce the actual shipping product, while they’re closer in spirit to fellow managers/leaders or an R&D team, the manufacturing mindset can only really make sense of engineering as the factory floor, and MBAs’ whole thing is looking for ways to extract extra pennies by optimizing manufacturing and distribution. They can’t actually do that with software, but they aren’t technical enough to know that, and it doesn’t stop them trying. So, “ghost developers” — which, of course, is just engineers writing good docs, being in meetings, talking to customers, supporting each other with code reviews or pairing — seems like gross inefficiency because it looks like a factory producing fewer LOCs than companies are paying for. Remember how, when Elon took over Twitter, we’d hear about him asking coders to _print out_ their latest contributions to the codebase, and if the pile was too short they got fired? Elon is a manufacturing guy, not a software guy. Even the “Stanford researchers” part is MBA culture gone wild — they have _no idea_ what’s involved in making software, and can’t even talk to their teams effectively, but they think their dumb mindset is “science” and now they have “research” telling them they could fire half their teams and be more productive. 🫠

1

Finding it hard to keep up with everything going on in frontend and full stack web development? The latest issue of my Jamstacked newsletter goes out in a couple hours and it has all the framework/library updates and tutorials you need. Sign up here: https://lnkd.in/e8mcztqz #webdev #frontend #fullstack #jamstack

8

I’ve been a bit sick lately, but I hope to start releasing my next ZIO video course later this week. Until then, here’s a little blog post about logging in ZIO, including creating your own custom log format to get the output to look the way you want it: https://lnkd.in/e_6rB4ej The output from the code looks like this: timestamp | INFO | zio-fiber-249876708 | Basic log message| timestamp | INFO | zio-fiber-249876708 | Info level message | timestamp | WARN | zio-fiber-249876708 | Warning level message | timestamp | ERROR | zio-fiber-249876708 | Error level message | (The ‘timestamp’ field shows the actual date and time, but it’s long, so I omit it here.) #scala #functionalprogramming

17

There are also a couple of 'tap' examples at the end of the blog post, if you want to see how to use them in logging.

6

Server-Side Rendering (SSR) might sound technical, but it’s a game-changer for your website. Imagine faster load times, improved SEO, and a vastly smaller carbon footprint. Instead of your browser doing all the work, SSR lets the server handle it, speeding everything up. Our amazing team at RY have developed this feature and built it into our Umbraco offering, so all our clients can enjoy these great benefits! I will be covering this and more at Umbraco codegarden next month... #Umbraco #Codegarden #RY Read below!

28

2 Comments

Every time I pull on the "Oh, you must be using them wrong" thread with "A.I." coding assistants, it seems to lead to a lower quality bar. That's the "prompt engineering" secret sauce, apparently. Care less. I did actually say I was afraid this is how Gen A.I. would play out over a year and a half ago. I wasn't afraid that they'd be able to do my job; they clearly can't. What I was afraid of is that execs and investors won't care that they can't.

46

10 Comments

Developer downtime: don’t overwork your devs. It’s memorial weekend and I’m lazily sitting on my porch. My kids keep coming in and out of the house, but get stuck because the sliding door keeps coming off the rails and won’t open. Well, since I’ve got nothing else scheduled for the afternoon I investigate the issue. Turns out sliding doors have a bunch of adjustment screws. I adjust them till the door slides smooth. Left in the broken state my kids learned to hit top left side of the door before opening it. Bringing this back to work, I know customer success teams that have a cheat sheet of these maneuvers. Give devs space to observe, we naturally fix these issues.

15

1 Comment

It'll never be this obvious, but when you're cooking without expert design, you and your engineers will end up JUST LIKE THIS. It's more subtle these days: Missed sprints Unforeseen edge cases Confused customers Broken promises Refund requests Bandaids everywhere Alarming churn Feature bloat Rabbit holing "Nobody gets it, maybe we need an onboarding tutorial!?" ^^ Don't end up in "Panic Land." Get design help now and get it from folks who have been shipping products and building businesses for over 2 decades. #productdesign #apps #SaaS #startupdesign #startups #UX #UI #Productmanagement

9

1 Comment

No answer, just a question: where is the line between tenacious and stubborn? Tech writers have to be tenacious to get all the info they need to write up about 1/5th of it for the customer. We have to check multiple sources (you'd be surprised how many times two different subject matter experts disagreed about basic facts regarding a feature) and not give up until we find some evidence of the "gold file truth." But the flip side of that tenacity is that we can get dug-in to the worldview we worked so hard to create. For example, my bedrock belief that everything boiled down to a database somewhere was not useful for integration software. So how does a tech writer know when she's being tenacious vs. being stubborn? Photo of my stubborn Rocket J. Squirrel kitty, who stubbornly pushes my books closer to the edge of the desk with every sleep session. A desk I have stubbornly refused to clean up for months now...

6

5 Comments