Daniel Rice

@realJackJWyatt @fasc1nate I dare you to challenge him. Challege him!!!

@fasc1nate "Prince, man. That boy can ball!" - Charlie Murphy

Prince stands victorious over Charlie Murphy during a game of basketball, 1985.

@adcock_brett People don’t hop jobs when they’re paid competitively and treated well. Maybe look at your compensation packages and rethink how you hire if retention is a problem.

I often see resumes where someone has worked at 6 companies over the last 10 years. I'm staring at one right now. These job-hoppers usually last a little under 2yrs per company on average. If someone has a jumpy resume, it's the first thing I notice. It's so blatant to me, yet it continues to fool a lot of people. Thinking back over the last 15yrs at my companies: I've hired thousands of people, and I can't think of a single person I've hired with a jumpy resume who has worked out long-term. Not one.

do you ever look at someone elses code and get so pissed off you need to go cool down?????

Alot of people say Atlanta is full but did you know the city of Tokyo is half the size of Atlanta and has x6 times the amount of people?

So, let me get this straight. You just got out of college, and you think every system needs to be distributed? That's your big revelation? Let's think about that for a second. Distributed systems are complex, they're expensive, and they're a headache to maintain. You ever heard of KISS? 'Keep It Simple, Stupid.' That's Engineering 101. You know what happens when you overengineer a solution? You end up with a mess of dependencies, network latency, and a nightmare of debugging. Ever heard of a single point of failure? Now imagine a dozen of them, scattered across different networks. Oh, so every system needs to be distributed? What about a local bakery's inventory system? You think they need their doughnut count on five different servers Read Lamport's 'Time, Clocks, and the Ordering of Events in a Distributed System', did we? Or perhaps Brewer's CAP Theorem? It's charming, but let's get real. Distributed systems are not a panacea. First, think about consensus algorithms. Paxos, Raft, Zab - they're not trivial. You've got to manage leader election, log replication, and handle network partitions and failures gracefully. Ever tried debugging a split-brain scenario in a distributed database? Then there's data consistency. Sure, eventual consistency sounds great in theory, but have you considered the implications for transactional data? Read Eric Brewer's papers on CAP and then tell me about the trade-offs between consistency, availability, and partition tolerance in a high-volume e-commerce application. Ever heard of a monolith? It's not a dirty word. It's a viable architecture for a vast majority of applications. Scaling is not just about handling more requests. It's about handling more complexity. So, before you scale out, scale up. Optimize your monolith. Profile your database queries. Cache your responses. These are your bread and butter. Next you're going to tell me that every application needs to be on the cloud, right? You read Werner Vogels blog and think you need cross-region replication for all your services. That it's cheaper and more scalable? That you can just spin up a kubernetes cluster and scale your application to hundreds of millions of users overnight? Did you know that Capital One misconfigured an S3 bucket and it led to a massive data breach? Over 100 million customers' data exposed. That's the dark side of cloud computing. Misconfiguration. It's not just about throwing data on the cloud and calling it a day. It's about understanding the nuances of cloud security. Capital One's breach wasn't due to some high-level hacking wizardry; it was a configuration error. Maybe use your own brain for once.

@debarghya_das I’m sure it works great on the first date too.

Man builds ChatGPT wrapper that just helps people respond to texts on dating apps. Charges $28/mo, makes $2.3M/yr and the business is selling for $3.5M. Engineers worry about technical moat and venture outcomes instead of building something users want!

@greg16676935420 Validate your inputs!

Life Hack: if there is a “custom” tip option you can sometimes enter a negative number and make your meal cheaper

@dhh South Park lampooned the absurdity of these types of one sided contracts #humancentipad. #youagreed

This is how you keep your developer ecosystem in line, paying the billions in yearly toll fees. It’s really despicable. To think this was the company Jobs once claimed to be the pirates fighting against the navy (monopolistic IBM, at the time). How the turntables turn 💀

@Dashcraft89 @repoles @aviflombaum @rails I’d love to know what you think the 15% is.

@repoles @aviflombaum @rails Rails is heavy on convention so it’s basically lightspeed developer experience and productivity for 85% of use cases. The last 15% is what can bite you though imo

2 days of work. Not bad for @rails. A job board app that has categories, companies, job posts that are unique, the job listings that make the job post active on the home page, rich text job descriptions, company logos.

@repoles @aviflombaum @rails This is easily achievable in two days with #RubyonRails.

@aviflombaum @rails You did all of those screens and functions in 2 days of work?

@dhh There’s a happy medium between here between “Ship It” and “Analysis Paralysis..”. I’ve consulted for a lot of organizations whose projects fail because they cant get to market fast enough. I’ve also worked with firms who ship prematurely. It’s a tough balancing act no doubt.

"We’ve become so used to digital services being malleable that we’ve confused the possibility of software updates with their necessity. Some software can simply be finished, and a lot would be better if it were." world.hey.com/dhh/finished-s…

@JenaGriswold Or any criminal act, for that matter.

Donald Trump continues to argue that he shouldn’t face consequences for his involvement in the January 6 insurrection at the U.S. Capitol. The presidency should not be a get-out-of-jail-free card for engaging in insurrection.

@GovofCO Agreed! I enjoyed a wonderful #powderday at Keystone today. The lifts are fast and my quads are now very sore!

Colorado's powerful gondolas and chairlifts are located throughout the Rocky Mountains and are perfect in the winter and summer for even more stunning views of the mountains that you can't get from the ground.

@gfodor @dhh Agreed. Tim Cook is an overrated accessories salesman and Apple has barely innovated on his watch. The Apple Card is a flop…

@dhh Apple needs a new CEO

Apple is protecting its App Store racket with the same kind of indignant entitlement that characterized Microsoft during its darkest monopoly days. They’re in full “cut off the air supply” mode in Cupertino, pursuing Epic for a $73m legal bill in a lawsuit they partially lost. But the red midst of vindictiveness is blinding Apple’s view of history, and making them repeat the mistakes it took Microsoft two decades to undo. It’s the ultimate monopoly irony too. Apple owes its entire modern existence to the fact that the DOJ was breathing down Microsoft’s neck in the late 90s. This legal threat made Microsoft desperate to prop up a semi-credible alternative to their Windows and Office monopolies, and Apple fit the bill perfectly. A basket case of a company, with an irrelevant, shrinking marketshare, in dire need of a lifeline. So in 1997, Microsoft invested $150m into Apple, and promised to bring Office and Internet Explorer to the Mac. Back then, these were crucial monopolies without which any platform would struggle. This saved Apple, but it didn’t save Microsoft. In Redmond, they were still bent on total domination. At the height of its monopoly power over the internet, Microsoft had an incredible 94% marketshare. It used this marketshare to seriously slow down the evolution of the internet, as it continued to perceive it as a threat to the Windows and Office cash cows. And it worked. They really did slow down the evolution of the internet, and even disbanded the IE team, once total domination was assured. But Microsoft’s brutish tactics also managed to turn an entire generation of developers against them. And the bill for that didn’t come due until Windows Phone. Nobody, and I mean nobody, wanted to lift a finger to help Microsoft gain a foothold in mobile. The wounds from the late 90s and early 2000s were still fresh in many developers minds. So many cheered as Apple went from underdog, favored by developers for their embrace of Unix roots in their operating system, to the dominant player on a new platform. Microsoft has had to work hard to undo that poisoned relationship ever since, and under Satya Nadella, seems to have broadly succeeded in that mission. Microsoft is no longer developer’s enemy #1, Apple is.  Now that’s not a universal statement, just like it wasn’t for Microsoft. There are hardcore Apple stans who will defend every atrocious monopoly abuse they commit, just like there were hardcore Microsoft stans doing the same in 2000. But the vibe has swapped. I don’t know of many developers brewing a burning hatred for Microsoft these days, but I know plenty of developers who feel like that about Apple. Apple would be wise to study the long arc of Microsoft’s history. Learn that you can win the battle, say, against Epic, and end up losing the war for the hearts and minds of developers. And that while the price for that loss lags beyond the current platform, it’ll eventually come due, and they’ll rue the day they chose this wretched path.

I've recently rolled out #Ruby 3.3 on a large #rubyonrails monolith that's hosted on #heroku. So far, so good. Thanks @rubylangorg Core Team for all you do.

@stevenharms @strzibnyj You have the wrong team if they can't iterate and write tests at the same time. Feel free to DM me or go to railsagency.com if you'd like to hire a better team (or me).

@strzibnyj I think tests are great post market fit, but while iterating they can slow the team down. Ie questionable value of testing an api with 0 users

I'll never understand makers hating on tests. Tests is the thing that makes you fast in the long term. I almost thought that a blog index page doesn't need one, indeed. But I am engineer, so I write them. And guess what? It caught an issue when posts had no content and I was doing something with an ActionText field. And it's the most basic test ever:

@lucianghinda Exactly. Having a culture around this is ideal.

Yes, it is of course a balance to be achieved about the effort that should be put it into testing on new versions vs progressing with the product. I like the approach of Shopify and others to continously run tests on the upcoming version of Ruby and thus keep an eye on what might happen when it will be released.

It is 2024 and Ruby 3.3 is out for about 2 weeks already. So let me ask you this: Why are you not using the new language features released since Ruby 2.7? What keeps you for adopting the new features?

@arkaflame @thoughtbot Preach.

@thoughtbot Another layer, on another layer, on another layer. Guys, just use vanilla JS or good old jQuery/Protottpe. You don't need any other thing.

We’ve built Superglue, a framework that makes Rails and React as productive as Rails, Hotwire, Turbo, and Stimulus. thoughtbot.com/blog/introduci…

@GAFollowers Move to Paris if you want to take the metro everywhere. Atlanta will never be like this. Thankfully remote work is a real thing and can dramatically lower commuting, traffic, wasted time, and reduce emissions.

What Atlanta could be without a car