“Dave is excellent at rapid development while keeping in mind the big picture. He is always learning new things and keeps an eye on the latest trends in many areas from Lean start up strategies to the latest technical tools. I can always count on him for collaborative creation of shortest-path solutions. It was a pleasure to work with Dave. ”
About
David Kuster is a microservices architect, senior backend software developer, and…
Activity
-
Behind each of these books is a hero, a mentor, a friend, or I should say, a combination of all of these titles. As I begin my transition to the…
Behind each of these books is a hero, a mentor, a friend, or I should say, a combination of all of these titles. As I begin my transition to the…
Liked by David Kuster
-
What started as a joke addition to my office wall (thanks to my sister) is starting to become what I think would change the world. The world doesn't…
What started as a joke addition to my office wall (thanks to my sister) is starting to become what I think would change the world. The world doesn't…
Liked by David Kuster
-
This is a really good article. https://lnkd.in/gkdZTJm6
This is a really good article. https://lnkd.in/gkdZTJm6
Liked by David Kuster
Experience
Education
Honors & Awards
-
Winner of Sega Genesis development kit from NEXT Generation and Shiny Entertainment (1994)
-
Winner of a contest sponsored by NEXT Generation video game magazine and Shiny Entertainment (both now defunct). This Sega Genesis development kit was used in the creation of the game Earthworm Jim. I received this along with a manual for assembly language programming on the Motorola 68000. Not much was accomplished with it but I was able to download ROMs from the web and play them on the kit. (This is too fun a bit of trivia to not include on my LinkedIn page.)
Recommendations received
2 people have recommended David
Join now to viewMore activity by David
-
Try your software interview process/questions on people in your company you already know are qualified for their position. Give them no time to…
Try your software interview process/questions on people in your company you already know are qualified for their position. Give them no time to…
Liked by David Kuster
Other similar profiles
Explore more posts
-
Alexander Reizer
There's an ongoing argument between product people and developers about "detailed requirements". Developers sometimes would like more clarity in requirements, or to have a requirements document that would leave no questions unanswered. Product people really want developers to be involved in the solution and help provide the most appropriate way (not just the way the product person can think about). I use various examples to show why this "tug of war" isn't realistic and no one side can win. Developers may expect to have a document which no one can misinterpret (which human history proved impossible) and product people may want developers to guess everything that they wish for, and no one would win. Then I ran into an article about a hit game called Baldur's Gate 3, which I think could be another great example to use. The video RPG game is based on D&D, Dungeons and Dragons, a tabletop game with a long and honored tradition (and a bit of a tendency to be played by "nerds", i.e. people who like to get down to the very last detail of everything). So, in that spirit, D&D has a comprehensive rule book, which the game director assumed would be the perfect guide for the game designers and developers. In their public retrospective at a recent conference, the game design director said: "We thought the job of the designers was going to be easy because we have a design document that was just the printed books." Pretty soon, they discovered that in fact "it was far less "easy" than the team expected: "It felt like it was going to be as easy as giving the books to the programmers, like 'let's just get it out there, very quickly.' Before you know it, we're deep down in community forums reading through people arguing what exactly was meant by a certain passage". Because when things are used, we discover what actually works and makes sense, and what doesn't. So despite having a QA's dream of a rule book, it wasn't a simple case of building the game according to that. They had to adjust it according to what people actually expected, and modify things according to how actual players most commonly modified things. So, if an award winning game, based on a pretty robust rule book had to do plenty of discovery and adjustments, so can your team building a category page for an e-commerce website, or a widget for "You also might like". It's just a part of building successful products, this level of involvement and cooperation is necessary even when things seem clear and well-described. Watch the actual retrospective on Youtube: https://lnkd.in/d3r8kZJ6 The article: https://lnkd.in/dyVintzY The rules of D&D example from 2014: https://lnkd.in/d5qSzXtb Most recent D&D rules: https://lnkd.in/dhM2sScZ
-
Allen Holub
People tend to look at budgets the wrong way, IMO. The cost of software development per unit time (your engineering-dept. budget) is trivial to figure. Number of people * salary * load. There. You're done. You'll pay that out even if everybody sits around playing Canasta all day. So, the question is NOT what engineering it will cost; it's how best to use people's time to get the maximum benefit from that investment. Instead of a project, think in terms of what to work on. Don't assign people to the work; bring the work to the people and let them figure out how best to do it.
30 Comments -
Jeffrey Baker
Software Engineers have been coddled for years. Strong demand for engineering talent has created a culture of entitlement. For years, you could get away with anything if you could write good code. That culture is changing. Want to score a new job? Show up in a collared shirt. Want to keep your job? You actually need to show up to your meetings. Remember, GPT 4o can write code as well. It also costs 20 bucks a month.... EDIT: This post really blew up! fraction.work will be hosting an event with Raymond Gan to talk about the good, bad, and ugly of AI and LLMs in software development. Disagree with my post? Join the event on Monday and voice your opinion. All are welcome https://lnkd.in/eqM6KgqQ
268 Comments -
Matt Burch
If LinkedIn post trending I've seen is to be believed: TDD seems to be making a HUGE comeback. It reminds me of when JS came back into fashion (a long time ago, kids) after being relegated to the pile of joke languages (an even bigger joke back then, JS-haters). For the longest time, it was "TDD solves everything and any opinions to the contrary are wrong". Then you heard nothing about TDD, not a peep. I think it was right around the time of DHH's post about TDD (below). Now, tada, it's back, and just like before, you're wrong if you don't have `I ❤️ TDD 4-EVA` tattooed on your lower back. Me and my team break all the rules and it would be hard (but not impossible) to convince me otherwise: - We only test end-user facing UX, full-stack/integration level. I'm not maintaining a test for MyServiceObject#convert_this if the method signature changes. I only care about the user experience. - Each daily PR must include coverage but big features behind a flag get coverage near the end. Each team member can do what they want but I'm not burning a day of complex mocking just so Product can say "whoops, that's not needed now". Coverage when it's showtime before the curtains go up. We are currently on Playwright + axe-core (for a11y compliance) and we love it. Migrating away from rspec + capybara (flakier than a bowl of frosted flakes). More on Playwright in another post (it's amazing). I don't think TDD is bad. I just want to mock things as few times as possible before a release, because test env data bootstrapping is a giant pain. To each their own, as long as your UX is protected.
4 Comments -
Suresh Ramakrishnaiah
Most of the tech folks talk about tech debt, also known as technical debt or code debt. There is another less known debt is "feature debt" hiding in plain sight, it is the cost of not implementing feature completely. At some point later these starts to bite your team, identifying these and fixing them will save lot of headache for your team in dealing with customer issues.
Explore collaborative articles
We’re unlocking community knowledge in a new way. Experts add insights directly into each article, started with the help of AI.
Explore MoreOthers named David Kuster in United States
-
David Kuster
-
David Kuster
Actively seeking Engineering / PCB Design position
-
David Kuster
Manufacturing Engineer at Service Steel- Tubing, Pipe and Bar Specialists
-
David Kuster
Environmental, Health and Safety Coordinator at Burner Systems International
7 others named David Kuster in United States are on LinkedIn
See others named David Kuster