We work with our clients in showing how software development should involve the whole team - avoid silos and barriers to communication.
π Learn more about the practice here: https://bit.ly/3MyyGqe
#DevIQ #ProgrammingPractices
Latest posts tagged with #DevIQ on Bluesky
We work with our clients in showing how software development should involve the whole team - avoid silos and barriers to communication.
π Learn more about the practice here: https://bit.ly/3MyyGqe
#DevIQ #ProgrammingPractices
π« Are you waiting until your app is painful before adding a feature?
That's what we're talking about here with Pain Driven Development:
https://deviq.com/practices/pain-driven-development
#DevIQ #ProgrammingPractices
π£οΈ Pair Programming and Continuous Integration create important feedback loops in #SoftwareDevelopment.
π‘Learn more about the importance of feedback in this #DevIQ article: https://bit.ly/3Xn9GbS
#PairProgramming #ContinuousIntegration
π We're good at telling others this, but we aren't good at doing this ourselves.
π Sometimes, you need to read the manual.
π Learn more here: https://bit.ly/4cJfz7N
#SoftwareDevelopment #DevIQ
π’Never lose sight of the fact that until you ship your product, it is not providing value to anybody.
Read more on why we think Shipping Is A Feature: https://bit.ly/3MIDvxa
#DevIQ #ProgrammingPractices
public int DosTuFf(int x, int y) => x+y;
If you find that hard to read, know you aren't alone! Check out our thoughts on code readability here: https://bit.ly/4gdlN2C
#DevIQ #readability #SoftwareDevelopment
Keeping a large team moving in the same direction without expensive communication failures is difficult, and this difficulty grows quickly with increases in team size.
π£οΈ Learn more about the growth of communication pains in #SoftwareDevelopment as teams grow: https://bit.ly/3AOxU5L
#DevIQ
AI acceleration is table stakes.
Predictable delivery is the differentiator.
DevIQ preserves delivery context inside your environment β no public models, full IP control.
Letβs talk at NAB.
#NAB2026 #NABShow #DevIQ #PredictableDelivery
With Inversion of Control (IoC), the flow of control within the application is not controlled by the application itself, but rather by the underlying framework.
π Read more here: https://deviq.com/principles/inversion-of-control/
#DevIQ #ProgrammingPrinciples
Defensive programming is the practice of anticipating problems that may arise in a software system and writing code to keep the system in a good state when such problems occur.
Learn more here:
https://deviq.com/practices/defensive-programming/
#DefensiveProgramming #SoftwareDevelopment #DevIQ
π "Perfection (in design) is achieved not when there is nothing more to add, but rather when there is nothing more to take away." - Antoine de Saint-ExupΓ©ry
Learn about simplicity and complexity in #SoftwareDevelopment #LeanProgramming #DevIQ
https://bit.ly/3Mw12kT
Unlock the power of the REPR design pattern in your software architecture! Learn how the Request, EndPoint, and Response model can streamline communication and improve your systemβs efficiency. π
https://deviq.com/design-patterns/repr-design-pattern/
#DevIQ #SoftwareDevelopment #DesignPatterns
R-E-S-P-E-C-T - Find out what it means for us in #SoftwareDevelopment: https://bit.ly/4cSmLyq
#DevIQ
In XP's Simple Design, the first rule is: Passes all tests. Code for functionality and reliability. No unnecessary fluff, just whatβs needed to get that green light!
Read more on Simple Design's rules: https://bit.ly/4g3SKhN
#DevIQ #SimpleDesign #XP
Test Driven Development, or TDD, also known as Test Driven Design, is a process for writing code using tests to define and then confirm the software's behavior.
Read more about TDD here: https://deviq.com/practices/test-driven-development
#TDD #DevIQ #SoftwareDevelopment
π° Vertical Slices aren't just for cakes.
π©π»βπ» Check out how you can take a vertical slices approach to software development here: https://deviq.com/practices/vertical-slices/
#DevIQ #ProgrammingPractices
Courage underlies several XP and Agile practices, and several practices are designed to increase how courageous the team can be.
β¨ Learn more about courage in #SoftwareDevelopment #Agile: https://bit.ly/3Xm6MEc
#DevIQ
Amdahl's Law serves as a reality check for those looking to improve system performance through parallelization.
Read on: https://bit.ly/3AwSibw
#DevIQ #SoftwareDevelopment
Any time one programmer calls another over to have a look at something they're working on, they're practicing pair programming. π¨π»βπ»π©π»βπ»
π Learn more: https://bit.ly/46XyV7G
#DevIQ #Agile #SoftwareDevelopment
π€ When it comes to conflicts in version control, how do version control systems handle it?
π‘Learn more about locking and merging here: https://bit.ly/4dydrkc
#SoftwareDevelopment #DevIQ
The Outbox pattern introduces a dedicated outbox table to hold pending messages, ensuring that they are only created if the associated business operation succeeds. π¨
Read on to see how to implement the Outbox pattern:
https://deviq.com/design-patterns/outbox-pattern
#DevIQ #DesignPatterns
The Outbox Pattern addresses the dual-write problem by storing both business data changes and outgoing messages within a single database transaction.
Learn how to work with this pattern in C#:
https://deviq.com/design-patterns/outbox-pattern
#DevIQ #DesignPatterns
In a distributed system, ensuring that messages are delivered reliably and consistently can be challenging. π©
With system failures, messages can be lost or not processed correctly. π₯
Learn how the Outbox pattern can help:
https://deviq.com/design-patterns/outbox-pattern
#DevIQ #DesignPatterns
Zombie records? π§ββοΈ
Ghost messages? π»
Message loss? π₯
It doesn't have to be like this! Learn more about the Outbox pattern:
https://deviq.com/design-patterns/outbox-pattern
#DevIQ #DesignPatterns
The Outbox design pattern is a messaging pattern that can be used to ensure data consistency and reliability in distributed systems.
π Learn more about how you can work with this using C#:
https://deviq.com/design-patterns/outbox-pattern
#OutboxPattern #DesignPatterns #DevIQ
π€Variable naming got you ? Don't be that dev who uses one-letter names! Clear, descriptive names are your friends for readability & future you will thank you.
Learn more: https://bit.ly/3YSCAlp
#ProgrammingPractices #SoftwareDevelopment #DevIQ
Classes with implicit dependencies cost more to maintain than those with explicit dependencies.
Learn more about the explicit dependencies principle: deviq.com/principles/explicit-depe...
#DevIQ #SoftwareDevelopment
π When in doubt, leave your code better than you found it!
πΆ Learn more about this principle from scouting here: https://deviq.com/principles/boy-scout-rule/
#DevIQ #SoftwareDevelopment #CleanCode
We work with our clients in showing how software development should involve the whole team - avoid silos and barriers to communication.
π Learn more about the practice here: https://bit.ly/3MyyGqe
#DevIQ #ProgrammingPractices
π« Are you waiting until your app is painful before adding a feature?
That's what we're talking about here with Pain Driven Development:
https://deviq.com/practices/pain-driven-development
#DevIQ #ProgrammingPractices