Kalle Varisvirta

Is there a difference between 👨‍💻 male and 👩‍💻 female developers? I believe there is, as our behavior naturally leads to significant differences that are reflected in our daily work. What do I mean by that? 💡 Women developers often emphasize collaboration 🙋‍♀️, communication, and consensus within teams. They focus on code readability, thorough documentation, and adhering to best practices for maintainability. They may prefer proven solutions 💁‍♀️ over new technologies to minimize risk, and they prioritize a balanced work-life approach, handling conflicts with empathy and understanding. Male developers 🙋‍♂️ may lean towards independent work and prioritize problem-solving over discussions. They tend to focus on functionality and performance, sometimes at the expense of documentation, and are more open to experimenting with new technologies. They may work longer hours ⏳, prioritize career development, and approach conflicts more directly and assertively. Do you agree with my assertions? 💬 Share your thoughts in the comments! #womenIntech #frontenddeveloper #softwaredeveloper #girlscoding #techcommunity

5

2 kommenttia

I've just checked the new updated BambooHR UI and just want to say thanks for rounding every single corner. Glad to see that company is focusing on most important stuff. One small thing, though.. Why not use 5 minutes of a single developer work to actually fix the usability of timesheet entries?? Here, I've made it usable for you, free of charge: - user can distinguish weekends from workdays - "no hours" are grayed out to tell users it's "empty" - entered hours stands out and can be seen easily at a glance Again, I'm not an UX designer, so what's is your excuse? Are you guys not using your own system?

17

 🎉 Catch Viktor Grgic, the author of "Navigating Complexity of Cognitive Load in Software Product Development", who will be delivering a talk on "Overwhelmed teams and cognitive load". 🚀 Key takeaways: 1. Why reducing team responsibilities is a misguided solution that can worsen the problem. 2. How organizational structure has a large effect on the feelings of overwhelm. 🔗 Apply now to catch Viktor Grgic in the upcoming LeSS Conference Singapore 2024! https://lnkd.in/g-cqtZn8 #LeSSSG #LeSSWorks #Scrum

40

1 kommentti

Great post from Dan Harper below. Testing in Production! Worth reading if you're one of my Techie connections. The comments are especially constructive.

4

1 kommentti

I'm a mediocre developer. Oh wow, Sam, why would you write something like that on a public, job-related platform full of self-promotion and superhero-spotlights? Because it's true, and I'm fine with it, and that's actually a good thing. Being a mediocre developer and aware of that fact means that - I check every bit of code I wrote for mistakes (mostly test-first, because that makes it easier, which means I'm less likely to forget it) - I slice complicated things into small things that are manageable for my mediocre skills - I set clear boundaries to functionalities and make them do very little to make them easier (once again to help my mediocrity) - I add examples and explanations to my classes and functions so when I forget why I wrote them that way, I can re-read it (I have a mediocre memory, too) - I change as little as possible at the same time and take complicated changes very slowly - I reach out for feedback from other professionals to see if there is room for improvement - I use tools and automation to help me do things correctly (you know, not like that meme of the olympic pistol shooter guy from Turkey) - I read other peoples books, thoughts and code, so I can learn how others approach things The funny thing is: These practices seem to actually help improving the quality AND speed of the projects I'm working on - especially in the mid to long run. When the digital superhero-cowboys (the hardcore code ninjas and 10x developers, you know) are long gone and the dust settled, the code I wrote with those mediocre skills, with those tools and aids and supporting practices, is usually still maintainable and running. Have a nice week :)

111

26 kommenttia

You know your product works when it makes your users lazier. Funny thing is that Husnain Javed and I built Aircircle during buildspace s5 and it is already creating value for buildspace builders at s5 irl. We are still in beta. So, if you want access, comment with "Aircircle". PS: Big feature drop today that will 10x the value of the notes you add. Launch post incoming. #networkingwithai #buildinpublic

26

11 kommenttia

At the highest level, for me, the development team productivity equation has two components: BANG and BUCK. Improving productivity then starts with either of two questions - how can we increase the value of the software created, and how can we reduce its cost? When you exclude developers from discussions around value (e.g., strategy, customer/user interactions, product design), and then demand greater productivity, you're asking them to do that with one arm tied behind their back. (And then, of course, tie the other arm behind their back by giving them no meaningful autonomy.)

17

4 kommenttia

Documenting composable commerce is hard. There is a plethora of different possible compositions. This forces you to write very generic or theoretical docs. But that's not something developers want. They want to have concrete examples that work with their setup. Ideally, something they can copy & paste, and it'll just work. That's why I came up with Alokai (previously Vue Storefront) customization guide for Next.js and SAP Commerce Cloud. Let me know what you think about it: https://lnkd.in/dyynF7HZ

45

3 kommenttia

💥 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 Ccpilot https://lnkd.in/ee9f6Y7s #microsoftazure #GitHubCopilot #microsoftadvocate

6

I'm so tired and, slightly, brain-dead from making full use of Frontend Masters today. I opted for the Git course and signed up for a workshop on testing. So I've been hopping from one to the other for about 8 hours so far. 🤔 Hmm, I just noticed that's a full workday! 🤣 Don't worry, I'll switch to straight up coding now. But during my last switch to the git course, I made an error! I had a moment of panic, then realized I've just been learning how to fix that. So learning for the win! If you were wondering, the error I made was in #vim, because I generally only use it in tutorials. Day 96's #impromptuvideos

12

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 kommenttia

A little story. Recently we've got a small customer request from an internal stakeholder team for expanding a service with a new functionality. Our dedicated architect spent a whole week to prepare a bunch of arguments why this task will require a total reconstruction of existing platform. But the truth is that development team already made that change in 2 days, and the customers were in tears of happiness closing important deal. It's the one side of the medal. But also I know teams who believing in strength of Agile, uselessly wasted time, budget and resources. Just because they initially incorrectly designed the system, not taking into account existing constraints and limitations. There is no a silver bullet. However, there are experience, best practices and common sense. I've chosen "Continuous Architecture in Practice" to expand my knowledge in Architecture topics, but this book is mostly about general Agile principles in architecture and non functional requirements. The entire book can be shortened to six principles (other parts are wordy explanations of these obvious postulates): - Principle 1: Architect products; evolve from projects to products. - Principle 2: Focus on quality attributes, not on functional requirements. - Principle 3: Delay design decisions until they are absolutely necessary. - Principle 4: Architect for change - leverage the “power of small.” - Principle 5: Architect for build, test, deploy, and operate. - Principle 6: Model the organization of your teams after the design of the system you are working on. If you have free time, take a look at this book. It wouldn't hurt. ★★★☆☆

2

Lately I've been tinkering with a curious little hobby project: Building a hosted search service in Node.js, powered by Luca Ongaro's MiniSearch, to facilitate out-of-process indexing and searching of Umbraco content. I'm quite pleased with the result - even if it's not quite production ready 😆 All the details are in my latest blog post 👇 https://lnkd.in/dSZsHNx7 #umbraco #headless #nodejs

10

Interesting talk, especially the roast of scrum in the last 12 minutes - calling it an outdated way of organizing work now. He also claims scrum makes things take months instead of hours - good compared to earlier techniques that made things take years, but slow compared to methods that allow work to be done in hours. He also supports frequent re-teaming and laments all other agile methods being completely forgotten when scrum somehow grew into industry standard. The rest of the talk is also quite interesting. https://lnkd.in/d_2fa6nT

1

I heard a story yesterday from a new friend about an unsuccessful software development project that lasted for 1.5 years. It is over 1.2M USD in total budget spent to date and still needs to be finished. How do I know it's not successful? The phrase that he said: "They will probably deliver it this Autumn, but it will be a very raw product that no one needs" So, what went wrong? First of all, the contractor's choice. They selected a large software development agency with offices in 10 countries, and that seemed trustworthy. What you can expect in this case? - You will get your product done with a good quality - You will pay 30-50% more than for small consultancies - You will have a chance to meet someone in person somewhere in your country - Your product will be finished (but you obviously need to pay for every hour worked). What's the downside except the price? One main thing: Your product will be your responsibility only. Was your idea bad? Well, you paid 1.5M to validate it; no one really cares if something built will never be used. In 2V Modules, we have a different approach, which I'm a big fan of. If we start working on something, we dive deep to understand what this product is for, what pains we are addressing, who the ICP is, and whether it was validated or not. Even if it's an "internal" product, there are still multiple ways of building it. It's not only about the business analysis stage, it's about finding the right solutions. So I think small teams are often a better fit because they actually CARE what they are building, not only HOW it is built.

11

2 kommenttia