Sullivan | Software Engineer @SullivanJosh2

Software Engineer | Architecting Optimized & Resilient Systems | Building Scalable Solutions for businesses | System design and Architectural thinking. portfolio-qt08.onrender.com Joined June 2019

Tweets

2K
Followers

436
Following

3K
Likes

3K

Sullivan | Software Engineer @SullivanJosh2

3 weeks ago

@Akintola_steve KYC, Biometrics, Daily withdrawal limits are all proper consideration for this

1 1 1 114 0

View Details

Sullivan | Software Engineer @SullivanJosh2

4 weeks ago

@Identity_Crisiz @Akintola_steve What didn't happen

0 0 0 10 0

View Details

Sullivan | Software Engineer @SullivanJosh2

4 weeks ago

@careerspeakshq There is no application Link. Is there an alternative?

0 0 0 34 0

View Details

Sullivan | Software Engineer @SullivanJosh2

4 weeks ago

@Akintola_steve Three common ways - visibility, referral and a great job done to a previous client. Visibility - your growth is known and trusted Referral - Some has trusted you already completed Jobs - your great work is speaking for you

0 1 0 186 0

View Details

Sullivan | Software Engineer @SullivanJosh2

4 weeks ago

@IamAroke There is a fundamental difference. Arguments are values passed to function during function call. Parameters are values received by the function that will be used in the execution

1 0 2 466 0

View Details

Sullivan | Software Engineer @SullivanJosh2

4 weeks ago

@Mohd_Danishtech Interested.

0 0 0 29 0

View Details

Sullivan | Software Engineer @SullivanJosh2

4 weeks ago

@Akintola_steve Each chose between consistency and eventual consistency comes with a cost. Speed or latency. You can't have both. I wouldn't chose as a favorite - I will chose according to what could hurt the business. Speed on features that stale data don't hurt user and business else slower.

0 0 0 11 0

View Details

Sullivan | Software Engineer @SullivanJosh2

4 weeks ago

@Akintola_steve I believe this should be a per feature level decision and not a system level decision. They are features that requires strong consistency and others, eventual. Instagram reels could be eventual and wallet balance strong consistency. You chose by feature and as a system.

1 0 0 20 0

View Details

Sullivan | Software Engineer @SullivanJosh2

4 weeks ago

I watched a junior ecstatic that he wrote a great code as he showed me. I asked him, why will a page need to refresh before the latest update/delete is seen? Silence. Told him, go learn filter and map methods in JS. Understand engineering before using AI heavily.

0 0 0 24 0

View Details

Sullivan | Software Engineer @SullivanJosh2

4 weeks ago

@MansiCodez Make the request idempotent

0 0 0 341 0

View Details

Sullivan | Software Engineer @SullivanJosh2

4 weeks ago

A junior developer met me wuth his codebase. For a single page, I saw 2,000 lines of code. I told him the codebase looks so overwhelming. He watched as I turn it into 8 lines of code using components to separate concerns. Be strong with the fundamentals before using AI heavily.

0 0 1 71 0

View Details

Sullivan | Software Engineer @SullivanJosh2

4 weeks ago

As simple as this will appear, "Design a great production-grade user registration". Let's see your engineering thinking.

0 0 0 15 0

View Details

Sullivan | Software Engineer @SullivanJosh2

4 weeks ago

@IamAroke You are the only one boss. It is the best thing that happened to engineers in debugging. Finally for frontend development for spinners is great.

0 0 0 5 0

View Details

Sullivan | Software Engineer @SullivanJosh2

4 weeks ago

@MansiCodez Replication is having copy of database in the same machine - it uses leader-follwer pattern to distribute load. It helps in high reads while sharding is splitting the database into lists on different machine. Sharding mostly helps when write is the bottleneck

0 0 1 53 0

View Details

Sullivan | Software Engineer @SullivanJosh2

4 weeks ago

@smartnakamoura Micro service solved more of organizational problem than technical one. It becomes relevant when the team grows, services needs to become independently deployable, different stacks in the project - you start extracting services.

0 0 0 6 0

View Details

Sullivan | Software Engineer @SullivanJosh2

4 weeks ago

@IamAroke Circuit breakers - this gives the dead service a chance to recover without hindering other services.

0 0 1 30 0

View Details

Sullivan | Software Engineer @SullivanJosh2

4 weeks ago

@e_opore Micro service doesn't solve any technical problem. It solves an organizational problem. As a start-up, start with monolith. When the team grows, independent deployable services, different stacks being used, you can start extracting services

1 0 1 11 0

View Details

Sullivan | Software Engineer @SullivanJosh2

2 months ago

@Femiforge You mean understanding syntax, methods, algorithm and sorting algorithms, tailoring implementation to protect requirements. AI reduced workload for Engineer so they focus on core engineering. Even with AI, you can still be a bad engineer

0 0 0 3 0

View Details

Sullivan | Software Engineer @SullivanJosh2

2 months ago

@Akintola_steve The truth is this, I only watched a tutorial explaining the settings and usage of AI agents with a project I wasn't strongly invested on. Others, Copilot code suggestions is enough for my projects. I am still amateur in using coding agents. I love thinking man