Victor Argote

Slowly but surely, our goal is to use our social presence (particularly on professional networks) to define process. As process drives successful outcomes in technical initiatives, and as information tends to be more practical with empirical fidelity, perhaps a great starting point for us is to define our process to those interested. Getting started on software projects takes time and deliberation. While coders can "code fast" they need to "code purposefully". Data engineers need to have, well, data. Data and UX need to have a unique sense of harmony as (and this is a bit of an infinite jest in our field) we not only need to have the data but need the data to be produced by real people or processes. Design needs to strike a balance between humanization and practicality in cognitive systems and, at the end of the day, all of these elements need to play nicely. The start? Discovery. DO IT WELL. 🏴‍☠️

5

Just so you know, with Angular's standalone components, if you have to import a module 10 times, Angular will only import it 1 time when building out the page.

10

2 Comments

crypto market been going sideways too long. might need to get a real job. w/e business/technology problem you think you have, i'll solve it. and much faster than you thought possible. DMs are open. #react #nextjs #nodejs #javascript #typescript #ai #solutions #fullstack

5

One of the biggest problems I’ve faced is working with incomplete SDKs or ones that only support specific languages. Are there any people working on projects to automatically maintain and develop SDKs across major languages? #VC #devtools

3

2 Comments

Copilot and development: What activities are easy to automate? Hear what Marcel Chabot - Development Manager at The TM Group, Inc. uses Github Copilot for: - Writing up to 50 lines of code - Clean up long and complex code - Write documentation - Explain what the code does How have you been using Github Copilot to make your job easier? Want to see the full 34min interview? Click the link in the comment section. Dynamics Compass #github #copilot #microsoftcopilot #msdynamics #microsoftdynamics #msdyn365 #d365

2

1 Comment

This one reminds me of one of those rulers you'd use like once in elementary math classes. Anyone know what those are called? I was trying to search for it with no success. #cssbattle #cssgang #css

16

4 Comments

If I wrote a book called "Typescript, RxJs, and the Angular Paradigm," based on the ideas I write here about sticking as close to "The Angular Way" as possible, including Typescript and RxJs, how many of you would buy it? Because I might have been given an opportunity to write it.

22

11 Comments

Relying on a 'panic PIN' feature during an armed robbery might sound clever, but it’s incredibly risky. Armed robbers are unpredictable, and any mistake could cost lives. Simply trying to enter a wrong PIN or outsmart them isn’t worth the danger, especially in situations where medical care is almost nonexistent. It's better to let go of the money than risk your life. A smarter approach? Don't keep large amounts in bank accounts accessible through your phone. Instead, spread your funds across accounts, keeping some in places you can only access in person. Safety first. 💡 #StaySafe #FinancialSecurity"

6

If Not React, Then What? Frameworkism isn't delivering. The answer isn't a different tool, it's the courage to do engineering. Code that runs on the server can be fully costed. Code that runs on the client, by contrast, is running on The Devil's Computer. As a result, an unreasonably effective strategy is to send less code. In practice, this means favouring HTML and CSS over JavaScript, as they degrade gracefully and feature higher compression ratios. Declarative forms generate more functional UI per byte sent. These improvements in resilience and reductions in costs are beneficial in compounding ways over a site's lifetime. Stacks based on React, Angular, and other legacy-oriented, desktop-focused JavaScript frameworks generally take the opposite bet. "Our product stack has bet on React and the various mythologies that the cool kids talk about on React-centric podcasts. You're asking us to rethink the whole thing. Which silver bullet should we adopt instead?" JavaScript remains at least 3x more expensive than equivalent HTML and CSS, byte-for-byte. The choice isn't between JavaScript frameworks, it's whether SPA-oriented tools should be entertained at all. For most sites, the answer is clearly "no". Sites built to inform should almost always be built using semantic HTML with optional progressive enhancement as necessary. Sites that have content that changes more frequently should look to "classic" CMSes or tools like WordPress to generate HTML and CSS. Blogs, marketing sites, company home pages, public information sites, and the like should minimise client-side JavaScript payloads to the greatest extent possible. They should never be built using frameworks that are designed to enable SPA architectures. Managers and tech leads that have become wedded to frameworkism often have to work through a series of easily falsified rationales offered by other Over Reactors in service of their chosen ideology. Note, as you read, that none of these protests put the lived user experience front-and-centre. "...it works for Facebook" To a statistical certainty, you aren't making Facebook. Your problems likely look nothing like Facebook's early 2010s problems, and even if they did, following their lead is a terrible idea. "...React is industry-standard" This is, at best, a comforting fiction. At worst, it's a knowing falsity that serves to omit the variability in React-based stacks because, you see, React isn't one thing. It's more of a lifestyle. Across more than 100 consulting engagements, I've never seen two identical React setups. There's nothing standard about any of this. It's all change, all the time, and anyone who tells you differently is not to be trusted. And if you don't mind me asking, how's that "CSS-in-JS" adventure working out? Still writing class components, or did you have a big forced (and partial) migration that's still creating headaches? https://lnkd.in/efB4PR-A

3

When you finally squash that bug that’s been haunting you for hours... 🕴️💻 Every developer knows this feeling 😌✨ Tap the link in bio to get SDE-ready and conquer those bugs like a pro! 🚀 #getsdeready #bug #developerlife #coding #softwareengineering #programminghumor #debugging #lifeofadeveloper #techlife #itlife #programminglife #programming #memes #fun #comedy #tech #developer #memesdaily #codingmemes #linkedin

3

I heard today that smaller companies tend to use JavaScript, while larger corporations tend to use typescript. Can anyone with more experience speak to this, and share why it is or isn't true?

1

1 Comment

Has anyone recently built an Android app using React Native version 0.76? I’d love to connect and discuss challenges I’m facing in the build process. If you’ve worked with this version or are currently building with it, kindly hit me up! Let’s share knowledge and collaborate. #ReactNative #AndroidDevelopment #MobileApps #mobildev

28

4 Comments

Serverpod continues to strengthen its lead in the Flutter server space with release 2.2! Being used by well known international companies as well as small startups across the world is a testament to its ease of use, power, and scalability. #flutter #makesbackendeasy

9

Another component challenge solved! Building or Designing simple components like these is like molding concrete blocks for a building project. This is my recommended approach to Junior Devs and Designers. Master the little components and then you'll be able to build more complex projects just by adding those little pieces together. See you at the top! #10xgoals

3

Lately, I’ve been splitting my HTML and CSS tabs in VSCode, and it’s been a game-changer for my workflow. This simple adjustment has made it so much easier to work more efficiently and maintain focus. It’s amazing how small tweaks can lead to a big boost in productivity. #WebDevelopment #VSCode #Productivity #CodingTips #Efficiency

3

When designing microservices, it’s tempting to dive straight into the details—databases, APIs, scaling strategies—but none of that matters if the core structure isn’t sound. That’s where Clean Architecture comes in. I just published an article on Medium exploring how Clean Architecture acts as a blueprint for building microservices that are maintainable, adaptable, and resilient. In the article, I cover: * The Basics of Clean Architecture: A quick look at the principles and why they matter. * Applying it to Microservices: From defining boundaries to layering services for flexibility. * Common Challenges: Finding that sweet spot between structure and over-engineering. If you’re looking for a practical approach to designing systems that can scale and evolve without collapsing under technical debt, this might be worth a read. I’d love to hear how you approach these challenges—what’s worked (or hasn’t) in your experience with microservices? Let’s chat in the comments. #CleanArchitecture #Microservices #SoftwareDevelopment #TechLeadership

3

 It’s long been a bone of contention that Oracle owns the trademark for ‘JavaScript’ but this marks the first serious effort to try and change that, including petitioning the USPTO, if necessary. You can support the effort by signing this open letter, joining a vast array of JavaScript luminaries. Click here to sign letter: https://javascript.tm/ #javascript #java_script #frontend #backend #nodejs

4

1 Comment