Carlos Eduardo Arantes Ferreira

There's been a lot of talk in the API industry lately about design-first versus code-first. Today Tom Akehurst from WireMock suggests a third option: prototype-first. "An API prototype, unlike a design document or specification, can be used immediately by its consumers. The client code is written, and app features are built early on," says Tom. Upfront design is usually a good idea for API development, but it's not always used in practice. So, could more dynamic prototyping allow the best of both worlds? What do you think? Check out his post on the Nordic APIs blog today for some thoughts about how to mock prototypes and the potential benefits of this approach. https://lnkd.in/eGqGeV7D

11

1 kommentar

Six months have passed since the extensive rollout of GitHub Copilot to Volvo Cars' developer community.​ "We expected significant efficiency gains of approximately 20%, but tasks like unit testing have surpassed expectations and seen gains of up to 40%", says product developer Sabina Edenlund, who sits on Volvo Cars' Gen AI committee.​ GitHub Copilot assists developers with testing, explaining, and generating code, and can support the advanced ‘autocompletion’ of coding. ​ ​ ➡ Learn more how Volvo Cars benefited from GitHub Copilot: https://lnkd.in/dPfGruTq #GitHubCopilot #DeveloperProductivity #MicrosoftAzure

1

A Key to Evolvable Software Architecture: TDD In many projects, the ability to adapt your software architecture is crucial. However, this evolution is impossible without evolvable code. One effective approach to achieve this is Test-Driven Development (TDD). TDD not only helps you craft understandable and adaptable code but also creates a safety net. Personally, TDD has been invaluable in my projects—a method I now consider indispensable. If I were to learn it today, I would seek guidance from a trusted expert. That's why I'm thrilled that Daniel Moka has developed a comprehensive TDD course. His expertise and trustworthy approach make this an excellent resource for anyone looking to improve their software architecture. For the sake of your projects and your code’s future, consider exploring his course.

3

1 kommentar

Here are the slides for my GopherCon.EU talk: How to Win Frames and Influence Pointers https://lnkd.in/d7byRQfu #gopherconEU #golang

71

4 kommentarer

"If it's boring - automate it. Release notes are boring" Whenever you ship a new release you probably need a release note, a report listing the new version number, fixed issues, new features… Why write all that manually? By building up your traces and recording your trails as you work, you can pull all this information out of your backend automatically. You’ve written your last release note. From here on out it’s release notes as code. --- This card is marked #intermediate in the #build area in the Continuous Delivery Metric Model Who writes your release notes? I've been in projects where developers and tech writes would spend weeks on updating documentation and release notes on the back of each release. But of course if you only have four releases per year then... No - wait! Maybe that's WHY you only have four releases per year!

26

2 kommentarer

TDD and the need for constant hypotheses. One of the things I love about following a TDD process is the fact that my brain must be in a near constant state of creating a hypothesis and then testing that hypothesis. Here are some examples, each of which pops into my mind before building/running the unit tests: "I expect all tests to pass, as I have a clean repo and I just pulled the latest code" "I expect all tests to pass, as I just added an empty new test" "I expect build errors, as my test is now calling a function I haven't written yet" "I expect tests to build and execute, but only my new test will fail, as my new function isn't performing the expected behavior yet" "I expect linker errors, as my function is now calling a driver function I haven't mocked yet for the host based unit testing environment" "I expect all tests to pass, as my mock is ready and added to the build and the function should be doing what I expect." BTW: I love it when I am wrong, as it forces me to learn yet more about the code under test.

23

1 kommentar

TDD and the need for constant hypothesis, continued: I expected this new test to fail, but it passed. Why? Check out the exact commit below in a repository where I am attempting to capture my TDD process in action. Curious about TDD? Follow along! https://lnkd.in/e7eh7h2q

8

Let's talk about Trust. Recently I just finished my skipper courses, and you know what - it's so much a software development. You're - a cross-functional team of 2-8 people - with a delivery idea of moving the vessel from point A to point B. But yet, that's an extreme sport - and as with every extreme team activity - Trust is key to success. A team member has the Trust if - believe other members are doing their best in their work - believe other member's estimations/promises are true - believe other members will raise a flag once trouble appears > We can fail, but fail quickly and learn. But how do you build that in the team? The first thing you do - you become such a person. You always do your best. You try to keep your word and promises. You fail and talk about that openly. You are - the Trust deliveryman. > As a leader, you need to trust your team first to be trusted. So what do you think? - Do you have a Trust-specific task in your backlog? - How do you measure the Trust in your team? - Did you have an experience where a lack of Trust became a blocker? inspired by https://lnkd.in/dGQCPi9v #LifeIsASoftwareDevelopment

19

2 kommentarer

Today in "developers now have so many things we can just stick together with minimal code": I added comments to my static site in about an hour (had to tweak the styling some) WITHOUT using a 3rd party service outside of my control (like Disqus). https://lnkd.in/gwkm-PBt If you want to comment on the post, obviously scroll to the below the content, where comments always live. :P. Or just reply to the mastodon post about it: https://lnkd.in/gePWPdRG The more I do with it, the more I believe in the Mastodon, the Fediverse, and ActivityPub. I still would like there to be some sort of smart new open_graph/activity_pub (og: ap:?) protocol that wraps https with a way to link out to a specified client, and for servers to return HEAD call annotated with the open_graph data. Maybe there should be a new http verb META that is HEAD plus the content of <head> (or at least <title and all the <​metas?

2

"If you think good architecture is expensive, try bad architecture" - Brian Foote and Joesph Yoder My take: My weekend reading, even though I don’t code anymore, I still enjoy exploring topics to stay informed and gain insights from experts in crucial domains. My past experiences have reinforced my belief that a company’s enduring success significantly relies on the quality of architecture crafted by our solution, data, and enterprise architects. While mastering this craft demands time, the long-term benefits make it a valuable investment. #softwaredevelopment #architecture

27

1 kommentar

Whenever I have to deal with legacy code, I know what to do. But how do you deal with building the culture in "legacy" teams? Let's take the example of legacy code: I know the algorithms, how to plan changes, what can be removed without regret, and the risks involved in rewriting and refactoring. It's so much more complicated with "legacy" teams—the ones you inherit, not the ones you create from scratch. Still, the process looks similar to dealing with a legacy codebase: 1. Assess and understand team dynamics through discussions and one-on-one meetings.  2. Define the desired culture clearly, just like setting a goal for refactored code.  3. Maintain clear documentation and open lines of communication to keep everyone aligned. 4. Recognize and reward desired behaviors to ensure everyone feels included. 5. Be ready to make tough decisions. A few members may not want to fit in a new environment. If they can't adjust, you may need to let them go. In the end, cultural change is an ongoing process that requires a structured mindset. Building teams is even harder than building platforms; platforms don't have feelings or unpredictable behaviors. How do you deal with building the culture in "legacy" teams? #teammanagement #engineeringculture #GR8Tech #igaming #sportsbook #igamingplatform

26

2 kommentarer

Kotlin's windowed function gives a sliding window view of a collection. It's a neat way to dissect a list and gather insights. Want to explore this more? Check out Functional Kotlin by Marcin Moskala.

7

I tested Confluence's new Live Edit mode with content and workflow management apps from K15t and Appfire so you don't have to. I summarized my findings in my #AtlassianCommunity article: https://lnkd.in/eumBnX2j #Confluence #AtlassianMarketplace #documentation #contentmanagement

20

Guys, if you're finding it tough to use git cli, I recommend you use Lazygit (https://lnkd.in/dxXW_jek). It's a great TUI alternative to just plain git. It also helps us understand how git works even if you are a complete noob. Also, to understand git and the commands and tools it offers, there is this crazy game named [Oh My Git](https://ohmygit.org/), introduced to me by my friend Yash D. that basically helps us understand git from a time traveller's perspective, and it is Amazing! Try it out!

2

1 kommentar

External caches are often considered when the existing database cannot meet the required service-level agreement. Unfortunately, external caches are not as simple as they are made out to be. Felipe Cardeneti Mendes examines the risks associated with external caches and how teams can achieve a performance boost and cost savings with a single solution. https://lnkd.in/gedwNpNf #ScyllaDB #caching #database #NoSQL

22

1 kommentar

Android Debug Bridge (ADB) How often do you interact with ADB? I guess you do it every day except weekends, as you follow the work-life balance (you do, right?). Let’s refresh our main knowledge about ADB. First of all, have a look at the image below. As a user, we interact with the CLI tool, adb binary. If you want to interact with ADB from your program code, Google provides a special Java-based library called ddmlib. In Marathon Cloud, one of the platforms that currently supports Android, we have faced many limitations with the only presently available developer API for interaction with the ADB server. Let me present some drawbacks of the ddmlib library: - All of ddmlib’s code is blocking (no async way). - Most of its commands spawn a new thread for each request (which can be crucial for RAM). - The code is not tested properly. - Most of the commands don’t use and don't provide some critical features such as timeout handling. That’s why one of our co-founders, Anton Malinskiy, developed a Kotlin-based and coroutines-using replacement for ddmlib called Adam. Have a look at the library here (https://lnkd.in/dWyyMH7z) and read the great intro article here (https://lnkd.in/dpHRBQ2w). Follow us to read more interesting details about infrastructure and UI tests.

3

Composable design makes your software simpler and more adaptable. - Your code becomes simpler. - You avoid duplication. - Your software adapts. Your software can adapt to situations you may not have imagined up front. I just published: Composing a Cup of Coffee from Components https://lnkd.in/gYtk3vkN Let me know what you disagree with. 😉 Read this post and more on my Typeshare Social Blog: https://lnkd.in/gWqnk7Q7

7

1 kommentar

Checkout my new #medium #Article which explains how to create, test and use a library in #Rust Create a library, test & use it in #Rust https://lnkd.in/ddv36mjm You're encouraged to code along and try something fun. I always appreciate a valuable feedback, so get back to me on which things I can improve. Keep an eye out for more and #follow on #medium as well. -- I am Ahmed Ali, Certified Blockchain Architect experienced in #Rust | #Golang | #Solidity | #Geth | #ZkP | #Blockchain #Infrastructure | Blockchain #Security team lead & #Auditor | #zkEVMs | #Rollups | #App-Chains | #Bridges | #Chainlink | #CCIP | #Layer 0,1,2,3 | #Staking | #DeFi #likeandshare for more

12