Fatima Sarah Khalid ✨

Web-based Drag and Drop interactions present difficult challenges for accessibility. In her latest post on the GitHub blog, Kendall Gassner breaks down the challenges and explains how the team here at GitHub solved them. https://lnkd.in/d-jGPk-d

62

1 Comment

“Let’s measure engineers’ productivity in lines of code written and hours spent on a task!” That’s a suggestion you’ll rarely hear at a company that values its engineers. Definitely not at Railsware. If that were the case, we’d miss the essence of engineering: problem-solving, innovation, and impact. Ultimately, productivity is about the solutions you create and the simplicity you bring. That’s why we always put quality first. Our engineers don’t rush to complete tasks. Instead, they take the time to craft thoughtful, efficient, and scalable solutions. That’s something no line of code or stopwatch can measure. In the end, it’s not about checking boxes. It’s about the impact of the work you deliver. If you want to drive impact and create lasting value, we’re always eager to welcome like-minded engineers :-)

36

Source: GeekWire From the article: "LinkedIn released its annual list of Top 50 startups, and three Seattle-area companies made it: Chainguard, Truveta, and Statsig." Additional articles are included in the first few comments of this post.  #Seattle #Technology #News #Chainguard #Truveta #Statsig

This is an important topic for the software industry and for open source in general. It's something that I think will come up a lot over the next few months as a theme, and it should be something to look into around what teams, companies, foundations and people as individuals choose to do. Avi's argument on sustainability for businesses and contributors is a good one to follow.

1

1 Comment

You're going to need more than one reference in your Sanity Studio schema types, trust me! Early on a project you might think one reference is going to be enough. But any relationship from one document to another, is more than likely going to benefit from two relationships eventually. Skip a future migration step and always use arrays of references!

26

8 Comments

Having a ton of fun writing an ORM for V2 of Case Kit. Typescript has such an incredible type system. I have autocompletion for column names, the ability to include relations, relations of relations, etc etc etc... all returning properly typed data (no classes in sight). It's been really satisfying seeing it coming together, and it's been great getting my hands dirty with some (relatively) complex generics. And to head off the obvious question… why aren’t I just using Prisma? Well there’s a couple of things I’m doing differently that I think are marginally better: there’s no code generation involved here, it’s just types (inspired by Drizzle); there’s no Rust binary you need to deploy, and it hews much closer to Postgres behaviour and syntax (the aim here is not to abstract away which database you’re using). But the real blocker to me using Prisma was that its extensions don’t support modifying queries of nested relations - a hard requirement for me due to the way I have multitenancy and soft deletes set up. It’s not shown in the video but the Case Kit ORM lets you write simple middleware that will be applied to every level of a nested query. Perfect for setting timestamps or adding clauses on tenant id or things like that.

21

Dare I say I'm a rails convert. It outshines any other full-stack setup I've ever worked with. And ruby (with rails) is just BEAUTIFUL. Exhibit A: 2 lines of code (no joke) to enable real-time updates for a given model (create, update, delete).

1

If you really need multiple backend repos before you have multiple teams question whether you should be multiple companies. If not you’re probably better off as a monorepo if so you’ve got bigger concerns. At UpContent we’re actively retreating from the architectural complexity of micro-repos, as a smaller team it’s just unnecessary and most tech these days support multiple separately deployable components/services in a mono repo. Exceptions might be tiny services that don’t hit your main db and for whatever reason are in another language. People always forget that part of microservice architecture principles were separate databases and no shared code. People also forget they were a way for large companies to segregate duties with fully autonomous teams each owning a service not a strategy for startups with one team. Multi-repo is a very valuable tool in the tool box but it is one for after your first team split and when you process in place to handle cross team coordination.

1

Unexpected excitement in my dev world today! A pull request landed on my desk, sparking curiosity. Little did I know it would lead to a mind-blowing revelation. With a simple click, I witnessed intricate brain processes unfolding live in my browser, all powered by R and webR. This fusion of neuroscience and web technology showcases the incredible possibilities at our fingertips. It's a testament to how far we've come in making complex scientific visualizations accessible and interactive. Truly, the future of data science and web-based analytics is here, and it's more exciting than ever! https://lnkd.in/gsnGk835 #DataScience #Neuroscience #RStats #Quarto #WebR

60

📚 Exciting news for all the Flow Engineering fans out there! Back in May, Steve's new book, "Flow Engineering," co-authored with his friend Andrew Davis, was released. 🎉 In June, Steve chatted with us about the inspiration behind the book. And now, by popular demand, we're bringing you a follow-up session where you can ask Steve anything about Flow Engineering! 💬 Don't miss this opportunity to dive deeper into the world of flow engineering with the experts themselves. Mark your calendars and get your questions ready! #FlowEngineering #FlowSession 🚀: Sign up: https://hubs.li/Q02JFL4s0

18

Today, we’re announcing the GA of GitHub Copilot Chat in GitHub Mobile–creating a world where developers can build on the go in natural language. By launching chat on mobile we are paving an avenue to a new way of working for the world’s developers. We are now far less bound to our laptops or stationary machines, enabling a freer flow of reviewing, approving, learning and creating software the go. After leading the GitHub Copilot team, today is also my first GA as the new Head of Product GitHub. And this underscores the vision Thomas Dohmke and I share: we will strengthen the GitHub platform, and make GitHub Copilot ubiquitous wherever the developer is on GitHub. Ultimately, with our Copilot-powered developer platform – and our latest advancements like Copilot Workspace –  we will enable a world with 1 billion developers, building from wherever they are. This is the future of software development. And I will work every day to enable this new horizon. Let’s build from here. 🚀 https://lnkd.in/eSutZVzP

223

11 Comments

I’ve recorded a few episodes of a new show I’m calling Commit History. Each 15-to-30 minute episode examines an interesting commit to a significant open source project. So far, we’ve examined things like how NodeJS added the fetch API, how a 25 year-old bug in Firefox finally got a fix, how the Zed editor sped up “select-all-matches” by a factor of 250x in a 75 line commit, and we’ve read commits in languages like Javascript, Rust, C++, Ruby, and Zig, with more to come. A lot of us got into engineering because of our curiosities - which led to tinkering, sometimes destructively, but always starting with an observation, asking ourselves “How?”, and pulling out the tools - either screwdrivers or terminal windows, and not stopping until we got an answer. I’ve long assumed those days were behind me, but recently I reflected on how often I dive into open source code, sometimes because an unexplainable bug keeps popping up at work, or documentation is lacking, or a top story on HackerNews caught my attention - and I find myself right back into that hacker mindset, digging deeper until I know how it works. I haven’t changed nearly as much as I thought I had. Commit History, so far, is just turning my camera on to record something I’ve done for most of my adult life. In each episode I’ve learned something new, and however simple that might sound, it serves as the bar to meet for me to publish an episode. If any of this interests you, you can subscribe to the newsletter for the show here: https://lnkd.in/gHHhZY9K

54

5 Comments

Thanks to the PGConf.dev conference team 🙏, the video of my talk at #PGConfdev is now live! Titled "How to engineer your developer blog posts to have a bigger impact," I share best practices for influencing people with your technical blog posts. With good English captions too. The tips in the talk are based on lessons from years working in engineering, product management, and product marketing. Think code reviews, requirements specs, and strategies to reach people even when they are busy with their own problems. Since some of my #PostgreSQL teammates have been nudging me to record this talk, I'm thankful to the PGConf.dev 🐘 #PGConfdev organizers (including Steve Singer, Melanie Plageman, & Jonathan Katz) for recording it for me! Watch the video here: 📺 https://lnkd.in/dXeCUmAa Is the talk useful? Also, what did I miss? I welcome suggestions for the next version of this talk. #Postgres, #blogging, #opensource, #databases, #writing

15

Non-software engineers can actually be like “some” software engineers. This is something I’ve already thought during this journey of technological change, backed by direct experiences helping companies solve real problems with software. Software is a solution to a problem. Thus, we usually need to understand the problem before starting to think of a possible solution. Traditionally, different people were dedicated to those different domains (understanding the problem and designing the solution). But things get a little blended nowadays. In some situations, non-technical members are in a better position to design (and implement) a solution. They just need to be a little technically-minded. The most effective solutions might actually come from non-technical individuals, as they possess domain expertise, which gives them a clear understanding of both the problem and their needs. With the help of modern tools, they are now able to create potential solutions themselves. The article is very interesting also because it basically demystifies the current adage about “we’ll all be replaced by AI agents” with a much more interesting take: “people can become more effective at solving problems” https://lnkd.in/de3b7vM5

7

1 Comment

We like writing engineering content Our engineers are at the center of what we build and our accountants experience. We're defining what AI-native looks like for accounting. We like writing engineering content because we want engineers who join us to know how we think about problems. This week, our very own Matthew Duong wrote a piece on Single Sign-On (SSO), breaking down the essentials and actionable tips (link in the comments) For founders, improving the login process and making it easier to access your platform means a simpler experience. For enterprises, it means reducing the number of passwords users need to remember, reducing the risk of security breaches. Shout out to Amer Taleb who joined us recently and took our content game to a new level. We have a lot more coming soon: new product features, employee spotlights, and our view of the AI Accounting space. Happy Friday from everyone at Truewind!

36

2 Comments

At the core of effective engineering leadership is the ability to stay connected with your team. This is perhaps the most challenging aspect because retaining the respect of your people is difficult unless you remain technically involved yourself. In my journey as an engineering leader, staying true to the individual contributor role that originally earned their respect has kept me close. This approach extends beyond technical expertise; it's about maintaining a deep connection with the core activities that propel product development forward at Gearflow. One of my biggest professional fears is becoming irrelevant or disconnected from my team and our work. This fear motivates me to continually reinvent and retool in response to market demands. Next month, I'll be sharing about my adventures generating synthetic data recently. And while I'm no expert when I start preparing for these talks, the process is incredibly valuable. It's less about delivering a perfect talk and more about how the preparation expands my thinking and exposes me to new capabilities. This helps me connect the dots to opportunities at Gearflow that bring real innovation to our customers. Speaking regularly holds me accountable and pushes me to learn ahead of the curve, ensuring I remain relevant and impactful day-to-day. Every talk is a journey of discovery, helping me to lead with humility, communicate clearly, and inspire a culture of innovation through a deep, technical understanding of our work.

20

☕️ Here's an entry from the Small Batches library: "Change your Perception". From Goldratt’s Rule of Flow (2023): [Controlling WIP] included some major changes, but I would say the biggest change was in our perception. We used to think that maximizing the efficiency of each resource, technician, or work station would yield the best global results. But now we know the local efficiency does not translate into global efficiency. Our primary objective is to maximize flow. Comment below on this applies to your daily work.

2

There's dozens of things you can talk about from yesterday's Google I/O. But the one I'm most geeked up about? https://lnkd.in/evwaMdCk Imagine this in education. You've got a book chapter that you're supposed to read and understand. You feed the chapter to this tool and it creates a 5 minute podcast highlighting the chapter done in the style of an interview. That's what we're looking at here. So frigging cool. #geekedup #googleio #education

52

1 Comment