Jake Dluhy

Got back into web design and hosting services. Currently building out a spec sheet of what I’d need for a “basic” to mid-tier server hosting… uhh farm? Needing for 2 businesses. So far the general Total price is just under $12k. Not too bad for what AI listed for initial setup. Back to CSS/HTML/JAVA.

Who are the best developers I've worked with? ✅ The issue I often encounter with developers is their lack of ownership over the product's success. Many think their job is just to write code and get paid. It frustrates me ❌ when some of my team's developers don't fully understand the product they're working on, its purpose, vision, and features. When a new developer joins Goaluin team, I emphasize the importance of being product-oriented and thinking from the user's perspective. As a developer, you should connect with the product, foresee potential issues, and celebrate its successes. To be product-oriented, you need to grasp the overall context of the product, use it, and consider all possible scenarios related to your tasks. I provide developers with enough documentation, including plain text, diagrams, Figma designs, and detailed information during conception meetings. However, good work requires more than just documentation. It requires proactive engagement. I can spot the best developers by their interaction in Slack DMs. I worry when a developer doesn't ask questions, misses overlooked details, or fails to catch conflicts with other aspects of the project. But when a developer actively engages with their tasks, I feel confident they will deliver quality work with fewer iterations. My guidance as a product manager has made many developers on my team feel comfortable sharing their suggestions, reprioritizing tasks, and even challenging my ideas about features. As a product manager, I rely on my team's input to make the best decisions. Just convince me. #developer #productmanagement #productdesign #startups #webdevelopment #programming

14

5 Comments

If you're a C# dev wanting to contribute to a great product and join a truly sick team I've been curating for the past few months let's chat. From CEO, CTO to Architect you will love the folks you're working for and they will unleash you. Product is a game-changer! Need a great C#/BE so this team can cook!!! 👨‍🍳 *US/GC only & continental U.S. is a must. #Csharp #dotnetcore #dotnet #backendengineer #rabbitMQ #postgreSQL #redis #docker #angular #typescript

16

2 Comments

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

I think many people in the software industry make the mistake of viewing tech debt like a loan in deferral. They decide to add to their debt assuming there is no short term cost, but one day they will have to start paying it down (or declare bankruptcy with a huge rewrite). A more accurate analogy would compare your tech debt to credit card debt. You immediately start paying for this debt. The minimum payment would barely chip away at the interest accruing. You pay that cost in your project with every feature. The tech debt you add today makes the feature you add tomorrow more difficult. Every work item you take on without addressing the debt will be more difficult, and will likely add to the debt itself. With both analogies, a common end result is crippling debt that grinds your progress to a halt. However, the former analogy assumes that you are making quick progress, when that simply isn't the case. "The only way to go fast, is to go well." - Robert C. Martin

14

🚀 Clay is growing really fast, and so is the surrounding ecosystem - agencies, experts, users, and Clay customers. After over 100 conversations, I've learned people aren't just adopting Clay to replace legacy enrichment providers. They're adopting and learning Clay because they believe: 1️⃣ Becoming a Clay expert is an opportunity to become an entrepreneur. Agencies are starting left and right to help fulfill demand from customers who want to implement or outsource running campaigns. These agencies are making really good money, growing fast, and are able to scale their businesses. Now is a perfect time to start, establish, and start to grow an agency. It's still early days... Some of the OG Clay agencies are The Kiln, Sculpted, ColdIQ, Growth Engine X, and many others... (I'm missing a ton here... so definitely drop your agency into the comments.) 2️⃣ The future of sales (and GTM) is creative. The old playbooks don't work as well anymore. The internet has never been noisier, and AI is making content creation ridiculously easy. The only way to standout & breakout is to think and build creatively. Clay isn't just a better enrichment or automation platform, we help customers go from idea -> execution so much faster and ENJOY doing it. By finding unique ICP data and creating workflows with almost any API, you can combine solutions to create unique customer touch points. I even saw a workflow that automated the creation of custom memes for prospects. 3️⃣ Learning Clay is a competitive advantage. It can accelerate your career and will increasingly be in high demand. There's even roles that are looking for GTM Engineers & Clay experts. A couple of my initial customers that only weeks into their deployment, are already having conversations with management about taking on more responsibility internally. Users are spending time to learn Clay inside and outside their organization. They believe this is the next skillset for GTM. I'm bullish that those who bring Clay into an organization will be able to have a greater impact & get promoted faster. They'll be able to help their GTM team think differently about GTM. 4️⃣ Clay is addicting and fun. When was the last time it was actually FUN to use a GTM tool? Humans need creative outlets. They yearn for it. And, Clay helps people unlock creativity. This is why Clay can be so addicting and fun to learn & use. Personally, I had burned out selling cybersecurity software. Joining Clay, and using Clay day-to-day to help customers, has provided me with an opportunity to be creative throughout the day. It's reinvigorated energy, helped my mental health, and made work fun again. It's amazing what creativity can do for you... Why did you start to learn & use Clay? P.s. if you're looking to learn Clay, subscribe to my newsletter for weekly tips, best practices, templates, GTM strategies, and free credits.

109

28 Comments

If anyone needs an engineering manager / front end JS and PHP skill set, DM me. Fwiw, and more abstractly: It feels odd to put out a feel for a “traditional” dev skillset when code is coding code on its own, and so many companies (including LinkedIn) are marketing “job retraining,” which is just code for the process of figuring out how to replace more humans with code.

2

1 Comment

Onboarding new developers well is critical. Here's what has worked well for me. 1. Get Developers Shipping Code Quickly One of the first things we do is get new developers shipping code as soon as possible. It helps them understand the workflow and reveals any issues with their environment or permissions early on. 2. Lean Heavy on Pair Programming Pairing new hires with tenured team members will help them navigate the codebase, understand our standards, and get up to speed on projects. 3. Training Culture Onboarding is a collective responsibility. This approach not only helps new hires feel supported but also strengthens the skills of our existing team members as they explain concepts and processes. What works for you?

17

4 Comments

Landmines in your software engineering career path: what NOT to do when applying for a role. Picture this: You've found your dream job listing. You're about to hit 'send' on your application. But wait. There's a minefield ahead that many don't see until it's too late. First, generic resumes. They scream, 'I didn't try.' Tailor your resume. Highlight projects and skills relevant to the job. Make them see you in the role before you even interview. Next, overlooking the cover letter. It's not just a formality. It's your narrative, your pitch, why YOU. Skipping it? Missed opportunity. Ignoring the company culture. Fit is a two-way street. A brilliant coder in the wrong environment becomes an unhappy coder. Research. Reflect. Does this place align with your values, your work style? Networking only when you need a job. Big mistake. Networking is about genuine connections, not just job hunting. Engage, share, be present. It's a marathon, not a sprint. Lastly, stopping learning. Tech evolves. So should you. Continuous learning shows you're adaptable, proactive. A huge plus. Avoid these pitfalls. Stand out for the right reasons. Engage below: What's one lesson you've learned from your job applications? Let's navigate this path together. #careerdevelopment #softwareengineer #winningresume

3

🪂 Some of the worst projects we've parachuted into have been led by a-hole developers. 📣 They are opinionated, loud, and dominate meetings. They are critical of other people's code and are often afflicted with Not Invented Here (NIH) Syndrome. 🚜 They tend to bulldoze through major architecture decisions and the rest of the team follows along, mostly because they fear their wrath. ⬆️ They also tend to fail up. They spearhead the massive rewrite of "legacy" code and when the cracks start to appear, they jump to a new role at a new company, touting their successes in the previous role. 🤢 Some of the worst architectures I've encountered were created like this: 1. Insisting no JOINs can be used in the database and nothing can be imported between Django apps because they might separate each one into microservices in the future (YAGNI). The result was terrible database performance as a result of serializing all the data whenever it crossed an app boundary. It required a months long rewrite to resolve. 2. Everything must be a microservice and ORMs are evil. This resulted in services sprawling all over which were undocumented and unmaintained. Schema changes were made manually and inconsistently so performance issues would crop up because an index had been added in one environment, but not another. It took the business years before they could reel all these all back in. ☢️ These people are so toxic to an organization. They force out the good people and leave behind a team that is too scared to share ideas or consenting views. Leadership tends get blinded in their smokescreen, so they put up with the bad behavior. 🪓 If you're a leader with someone like this on your team, LET THEM GO. It may feel like the business can't survive without them, but you'll be so much better off without them.

63

4 Comments

Jr. Devs, Looking at my TODO list for work this morning I found myself paralyzed. There was a lot to get done and many different priorities that I could place on each item based on availability, needs of clients, resources, etc. So… I just ordered them alphabetically and started working on them. Perfect? No. Moving forward? Yes! I know the amount of learning you face can be daunting. It’s often hard to know where to start or where to go next. Sometimes you just need to DO. Especially right now when getting hired may be somewhat out of the question for many of you due to the current market, analyzing the “best way” may keep you from moving forward at all. Find something that interests you and just start doing it. You never know what doors or new ideas or directions it might open up. #juniordeveloper #mentoring #do

8

1 Comment

not to brag... but I inspired Circleback to build a better Notion integration 💁🏼‍♀️ Here's a quick overview of how you can now add meeting note action items to any of your databases: https://lnkd.in/gWvZcrZ3

15

Does size matter? I mean the size of a Bubble Agency/software team. I've been on both sides—working with large teams and running my own small agency. Recently, I lost a project because the client preferred a larger team. Many think larger teams get things done faster, reduce risks, and have a broader knowledge base. However, in my experience this isn’t always true. More developers don’t always mean quicker results. There were times we were delayed by a some code or a feature that only one developer could handle, forcing other devs to be put on other projects. Smaller companies can be just as effective. They rely on strong connections and can quickly bring in additional expertise. While larger companies might treat you as just another number, smaller agencies offer more personalized attention and communication. In choosing between a large and small agency, consider more than just size. Look at their experience, flexibility, and ability to quickly source knowledge. Smaller companies can often compete with larger ones on these fronts. #softwareagency #softwaredevelopment #nocode Alchemy Apps

20

1 Comment

Will AI replace your average software developer/engineer? I have no doubt that this will happen eventually, and most of a developer's work will be replaced by crafting prompts for an AI to generate code. However, we are far from simply asking AI to clone an existing product or create an app with specific features. A couple days ago I stumbled on OpenDevin, an AI "software engineer". Before deciding to install and run it, I went online to see what people where doing with it and got jaw dropped by this video: https://lnkd.in/gi55_XtP where a developer asks Devin to work on a given task. At first glance, I thought Devin did a good job, if not the entirely correct one. Kept searching and found another video, a very good analysis on what happened on the first video and why Devin wasn't doing what was supposed to do https://lnkd.in/gBsJjxZS This doesn't mean AI isn't capable or that Devin can't write code or even generate revenue. We're simply not there yet. So, if you're thinking about building your next billion-dollar app solely with AI, remember that you'll still need coding knowledge to write effective prompts. ================================ Below it's a version of this same post, generated by Linkedin's AI given my content. It's good, but still, not me writing. Will AI replace software developers? While it's a possibility in the future, we're not there yet. Recently discovered OpenDevin, an AI "software engineer," which sparked curiosity. Watched a demo where a developer tasked Devin, showcasing potential. However, a subsequent analysis shed light on limitations. AI has potential, but coding skills remain crucial. Remember, AI isn't a substitute for coding proficiency. Check out the videos for insights: https://lnkd.in/gi55_XtP and https://lnkd.in/gBsJjxZS. #AI #SoftwareDevelopment #CodingSkills #Devin #OpenDevin #LLM #GenerativeAI

3

"Dev estimates" suck. (Coming from someone finalizing one for a client today...) They're never accurate. They give everyone heart burn. If your dev shop is giving you an estimate, it's going to be wrong. There are 99,000 things that come up when you are building software. So how does this play out for the client? “Oh so I have to pick between this really critical module OR a broken payment system?" So then - you're stuck. Your project money is gone. And you don't have a functional product to go to market with. What you should do instead? Pay for the time you need. Can’t pay? Get a technical cofounder (equity based). Prioritize your "core" functionality and those pieces should be FULLY functional. Stay close to the project, so you can relay real -time pivots and customer needs. Don’t fall into the trap - “It’s not perfect”. Just ship it, you’ll be saving money on the useless color debates and font styles since your product will change again and again and again. If you’re thinking through what’s next for your tech stack, development team, or general growth strategy, feel free to reach out and I’m happy to provide feedback.

9

On in-house systems I’ve seen this so many times; the team did all their testing in-house and they didn’t build automated regression tests because they didn’t want to spend the money on it. Read more 👉 https://lttr.ai/ARljS #softwaredev #SaaSBusiness #InHouseApp #SaaS #BusinessBuilding

2

An update for May 2024 on behalf of the .NET Foundation Project Committee... The most active Community projects for the past month were: Pull Requests - Orchard Core (139), OmniSharp VS Code (63) Commits - Orchard Core (119), OmniSharp VS Code (110) Contributors - Stride (5), Humanizer (4) Downloads - Polly (18.5M), AutoMapper (14.1M) Full list: https://lnkd.in/eV2Nmhae The most active Microsoft projects for the past month were: Pull Requests - .NET Runtime (612), Azure SDK for .NET (405) Commits - Roslyn (1507), .NET Runtime (423) Contributors - .NET Runtime (13), Azure SDK for .NET (11) Full list: https://lnkd.in/eyZnx9-W #opensource #dotnet .NET Foundation

52

1 Comment