Taylor Sampson

Any tips on getting a @nextjs + @turborepo setup to run a bit faster? Cold boot takes ~20 seconds. HMR is about the same.

Firewood pricing is madness. What does this have to do with buying tech services? I'll explain later. Back to the wood... Some charge per bag and attempt to put a weight on the bag. But weight of a bag of 10-20 pieces of wood can never be exact, and that difference can add up over dozens of bags. Others charge per piece. But pieces of wood aren't equal -- sometimes grossly unequal. When buying in bulk, there's an even more opaque idea of a "bakkie" load -- who knows what that is. I suppose the problem is inherent to the domain. Firewood is made by taking branches of varying sizes and chopping them into pieces with an axe. It's impossible, within that methodology, to achieve a consistent product, and thus to apply a consistent price to it. Buying technology services is not unlike this. There can be no single price for an 'app' because apps have different functions and are sized differently. But how do you attach a price to a function, or a size? What is 'size' when it comes to apps anyway? Pages? Endpoints? Services? It's inherently vague. I don't have the answers, but as a seller of technology services and a buyer of firewood, I lean on having a trusting relationship with my buyer/seller counterpart. If the price isn't exactly right, it's the context of a trusting relationship with open communication that will fix the price issue. If the trust isn't right, no price will fix it.

5

1 Comment

I've been thinking about the challenge of preserving the "low priority voice" as software products scale. As teams and projects grow, folks outside of development and product positions seem to get more and more quiet—or maybe they're just harder to hear. Sure, a typo here, some inconsistent spelling there; these don't really rise to the level of "bugs" since nothing's technically broken. But when these little things accumulate, they can start to chip away at the users' trust in the product and the company. Curious to know, how are others tackling this within their teams? #SoftwareDevelopment #TeamCollaboration #QualityAssurance

15

Our dev team uses Tailwind CSS on nearly every site we build. I've found it to be a significant productivity boost for two reasons: - The API is consistent and understandable - It reduces the time it takes to get up to speed when context switching from one project to project another In addition to the built-in utility classes that cover 90% of our needs, we use a small plugin to create custom variants to apply styles based on an element's state. I wrote a brief blog post that explains how we do it: https://lnkd.in/gVqEHAtp

2

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

🚀 Tech glitches that leave you scratching your head? 🤔 Curious how a rogue div led us on a wild goose chase? Check out the full story for a fun, techy twist on web development woes with a side of laughs.👇 #sitecorecontenthub #sitecore #WebDevelopment #TechHumor #AI #ReactJS #FrontendFails #epam

2

If culture fit isn't the most important aspect of adding another developer to your team I know you don't ship much. I follow so many small companies that out deliver large ones it's crazy. 3- 10 person teams, ship ship ship ship ship...Why? The mission is ____ing LOCKED in, everyone is on same page from character to keyboard. Let me give y'all hiring managers a tip. When you have those two candidates, one has ALL the tools technically but you vibe better with the other who wants the gig more? Hire the latter, train 'em up. That 4 week ramp up they need on 'X' will be well worth it long term, 100%. #softwarejobs #java #javascript #typescript #react #reactnative #vue #angular #svelte #astroJS #htmx #go #golang #rust #ruby #rubyonrails #scala #kotlin #closure #haskell #elixir #csharp #aws #azure #ai #aiml #tensorflow #python

7

3 Comments

Time to be fair.... In past posts, I have been less than complimentary of the DLC regulations that now make it more difficult to implement SMS into an application. I understand that all sorts of organizations use (and misuse) SMS millions (billions?) of times daily. I get that the new regulations make an attempt to reduce, as much as possible, SMS Spam. All in all, it just seemed like another example of hand-cuffing the good guys while trying to put some limits on the bad actors. My experience at the time was with #Twilio... and I tried to make it very clear that my frustration wasn't necessarily with them - they were doing the best they could to handle an avalanche of organizations trying to comply with new rules that everyone was stumbling their way through. I've been using Twilio for years and can't complain AT ALL about the platform performance for my particular small-scale needs. It was the nearly impossible approval process that really soured me. After nearly a year of living without application-based SMS (email only), I decided to revisit. The application was already all wired up for the feature - it was just dormant. This time around I was able to get up and running in 3 days... 99% of which was the DLC approval - which happened today. Kudos #Twilio for suffering through the tough days and making SMS once again something that can be done with very little pain. #twilio #sms #dlcapproval

2

Progress = your QA release process growing from 15 minutes to 5 hours. A stat that’s both invigorating & frustrating at the same time. But I think the single best thing you can do to delight your customers is to personally guarantee “it just works”.

10

Hey Turo, You have a major BUG in your dynamic pricing rollout. I explicitly turned it OFF after going through your training. I woke up this morning with a bunch of trips booked overnight because my listing was discounted by 70%!!! As someone who works in the industry and is very familiar with how feature rollouts work, there's no way this should have happened. (All of this was confirmed by Turo's customer support) This is not acceptable. I propose the following solution: Keep the bookings and Turo makes up the difference. It's not the renters or owners fault and this ensures no owners lose their All Star status or income. It also doesn't punish the renter for trying to take advantage of great deal.

1

1 Comment

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

Legend-State Over Redux? I recently connected with Jay Meistrich, the mind behind Legend State, and I've began using it on some projects. The speed and simplicity of Legend State has left me thoroughly impressed. No more dealing with reducers, dispatchers, etc. - just dive in and try it out! I love where this is going! Try it out! https://lnkd.in/gCpv_gS5 #LegendState #Impressed #Simplicity #StateManagement #Javascript

10

Tried react native expo. Pretty straightforward to setup as opposed to metro. Especially on Apple silicon. Plus it provides navigation based on file path like next js, which I think is pretty cool. Took me 5 minutes to set up as opposed to metro, which would take me a day at a minimum. It is also helpful to have a set folder structure before hand. #softwareengineering #reactnative #expo

13

“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 :-)

38

What are your views on enforcing code quality with new developers? OK, so you're planning on baking a cake for the first time. You probably didn't get it quite right. It might have been lumpy, uneven, or maybe it fell apart when you tried to frost it. Yep, that's how a software developer is when they are new to code. A newer developer may have code that's a bit crumbly on the edges while they learn the recipe. They might try it but don't quite get it right. Hey, that's not so bad. They're refining their skills and getting tuned to the new environment. But sometimes they may get a little sloppy and throw a few extra ingredients in or miss one or two. That's not so good. I don't know about you, but if I'm going to dig in to a delicious cake and find that the baker put anchovies in it, I'm not going to like it. And if I'm reviewing code and it has the same type of surprises with new glitches and missed requirements, I'm not going to like that either and it's going to waste everyone's time and effort. So you have to guide the developer and help them get better. You need to be firm but not discouraging. Keep your eyes on identifying the turning point where you no longer can accept that ruined cake, and above all else try to be a mentor and not a critic. To the newbies: Jump on in and don't shy away from the challenge. Show your best and learn from your mistakes. #CodeQuality #DeveloperGrowth #SoftwareDevelopment

9

1 Comment

If someone were to develop a new testing service from scratch for today's web and mobile applications...- What are the biggest pain points in your current testing processes?- What features would make your testing faster, easier, or better?- Are there particular integrations or tools you really, really like?

12

24 Comments

PSA - The !important (below) blocks the #JavaScript scroll eventListener. Yeah, who knew??! Note: Not my code. It came from someone else's #WordPress theme / work. html, body { max-width: 100% overflow-x: hidden !important; }

1