@kpuputti

typo system student

 Finland
kpuputti.fi/
Joined April 2009
  • Tweets4.6K
  • Following94
  • Followers388
114Media
Kimmo Puputti retweeted
Swarmia
@SwarmiaHQ9 Jun 2023
We love learning about other software organizations’ ways of working. And because we figured we can’t be the only ones, we wrote a comprehensive blog post about how we build software at Swarmia. swarmia.co/3WZJNNs
2
1
6
533
Kimmo Puputti retweeted
Swarmia
@SwarmiaHQ6 Jun 2023
Keeping engineers unblocked is one of the key responsibilities of software leaders. That’s why we’re launching Engineering Unblocked, a podcast where @rmurphey interviews leaders navigating the challenges of scale, complexity, and growth. Learn more: swarmia.co/3WVlWP4
8
1
11
1,954
Kimmo Puputti retweeted
Swarmia
@SwarmiaHQ29 May 2023
New in Swarmia: updated investment balance 📊 You can now navigate to the investment balance view from the stacked bar chart icon in the main menu. Then, drill up or down to look at your whole engineering organization, a group of teams, or a single team. swarmia.co/45Ndc1s
2
2
236
Kimmo Puputti retweeted
Ricky
@rickyfm3 Feb 2023
The reason all your favorite apps start to suck over time is because as engineering teams scale, the goal changes from building dope shit to building for metrics and there’s no known way to measure quality
22
84
7
956
84,769
Kimmo Puputti retweeted
Marco Rogers@polotek3 Feb 2023
Another blog post I've been sitting on for a while. A question I get asked often is how managers actually evaluate engineers. That's a long answer. But we can at least talk abut some expectations that engineers often overlook. marcorogers.com/blog/advice-…
7
67
15
287
67,532
Resilience is good, slack is good. Queueing theory FTW. jessitron.com/2023/01/16/res…
1
86
Code is a liability, happy teams and working processes are the asset. "If you can’t hold onto the original team, if you grow the team too quickly, you end up running to stay in place." baldurbjarnason.com/2022/the…
73
This reminds me of Arthur C. Clarke’s Fractals documentary I used to watch as a kid. Stunning!
saharan / さはら@shr_id13 Dec 2022
Life Universe oimo.io/works/life Explore the infinitely recursive universe of Game of Life! Works in real-time and is perfectly consistent, never fails to remember where you are and where you came from. 無限に再帰するライフゲームの宇宙を探索できる作品を作りました #indiedev
1
”We need founders who want to solve the problems that matter” wired.co.uk/article/europe-b…
Software companies aren't made of code. They're made of processes that produce and maintain code. And the foremost component of these processes are people. The code is just a by-product. More of a liability than an asset.
48
534
48
3,372
Plus, the funding environment. Around ~2010 it was “we have a mobile app” that opened investor wallets. ~2015: “we do machine learning.” ~2020: “we are building on the blockchain” ~2022 looks to be “we build AI” as things are looking. Good point @copyconstruct.
Cindy Sridharan@copyconstruct19 Oct 2022
Replying to @GergelyOrosz
Access to easy capital was also a factor, surely?
1
3
83
Kimmo Puputti retweeted
Nathan Barry
@nathanbarry27 Sep 2022
Struggling to connect on your remote team? We’ve built a 68 person remote team that’s driving $32 million in annual revenue. Here are 10 ideas for building great culture in a distributed team: 💻🌐
113
437
109
2,655
Hyvää Suomalaisen koodin päivää! Suomalaisen koodin edistäjä -palkinto 2022: @rikurouvila ja @koodiklinikka, onnittelut 💙! #KoodiaSuomesta #ohjelmointi #ohjelmistoala sttinfo.fi/tiedote/suomalais…

Suomalaisen koodin edistäjä -palkinto Riku Rouvilalle ja Koodiklinikalle | Koodia Suomesta ry

Koodia Suomesta ry on myöntänyt vuoden 2022 Suomalaisen koodin edistäjä -palkinnon Riku Rouvilalle ja Koodiklinikalle. Koodiklinikka on yli 4 500 ohjelmistokehittäjän verkkoyhteisö, johon ovat...

sttinfo.fi
9
3
25
Kimmo Puputti retweeted
David K 🎹
@DavidKPiano7 Oct 2022
I'm seeing a worrying trend of libraries/patterns that make it super easy to directly manipulate state, regardless of whether it's "physically" mutable/immutable. Sending events is more verbose, but it also makes updating data more predictable + understandable + safe.
3
1
31
I literally quit at my last job in the end of January and now noticed this. Was this a sign of something?!
2
6
Kimmo Puputti retweeted
Simon Willison
@simonw1 Oct 2022
Turns out I have a lot to say about this! I expanded my replies into a more detailed blog entry here: simonwillison.net/2022/Oct/1…
Gergely Orosz
@GergelyOrosz1 Oct 2022
A few software engineering practices which many teams will also consider "best practices." What other useful engineering practices would you mention? (Yes, getting back to working on @EngGuidebook!)
Software engineering practices is a term I’d suggest thinking of and using instead of “best practices”. Several tried and tested software engineering practices help with one or more dimensions of the software engineering process. Here are some of these: A written planning process. Before starting to code non-trivial projects, a plan is written and circulated for feedback. This plan might be called a Request for Comment (RFC), an Engineering Requirements Document (EDD), a Design Doc, an Architectural Decision Record (ADR) Automated testing. Writing unit, integration, end-to-end, performance, load, or other types of tests. This approach usually increases quality and maintainability and often results in less overall time to ship software, thanks to helping flag regressions quickly. Test-driven development. A subset of automated testing where tests are written before the actual code is. Code reviews. Before committing code, other engineers review and sign this off.

ALT Software engineering practices is a term I’d suggest thinking of and using instead of “best practices”. Several tried and tested software engineering practices help with one or more dimensions of the software engineering process. Here are some of these: A written planning process. Before starting to code non-trivial projects, a plan is written and circulated for feedback. This plan might be called a Request for Comment (RFC), an Engineering Requirements Document (EDD), a Design Doc, an Architectural Decision Record (ADR) Automated testing. Writing unit, integration, end-to-end, performance, load, or other types of tests. This approach usually increases quality and maintainability and often results in less overall time to ship software, thanks to helping flag regressions quickly. Test-driven development. A subset of automated testing where tests are written before the actual code is. Code reviews. Before committing code, other engineers review and sign this off.

2
21
2
111
Kimmo Puputti retweeted
Gergely Orosz
@GergelyOrosz1 Oct 2022
A few software engineering practices which many teams will also consider "best practices." What other useful engineering practices would you mention? (Yes, getting back to working on @EngGuidebook!)
Software engineering practices is a term I’d suggest thinking of and using instead of “best practices”. Several tried and tested software engineering practices help with one or more dimensions of the software engineering process. Here are some of these: A written planning process. Before starting to code non-trivial projects, a plan is written and circulated for feedback. This plan might be called a Request for Comment (RFC), an Engineering Requirements Document (EDD), a Design Doc, an Architectural Decision Record (ADR) Automated testing. Writing unit, integration, end-to-end, performance, load, or other types of tests. This approach usually increases quality and maintainability and often results in less overall time to ship software, thanks to helping flag regressions quickly. Test-driven development. A subset of automated testing where tests are written before the actual code is. Code reviews. Before committing code, other engineers review and sign this off.

ALT Software engineering practices is a term I’d suggest thinking of and using instead of “best practices”. Several tried and tested software engineering practices help with one or more dimensions of the software engineering process. Here are some of these: A written planning process. Before starting to code non-trivial projects, a plan is written and circulated for feedback. This plan might be called a Request for Comment (RFC), an Engineering Requirements Document (EDD), a Design Doc, an Architectural Decision Record (ADR) Automated testing. Writing unit, integration, end-to-end, performance, load, or other types of tests. This approach usually increases quality and maintainability and often results in less overall time to ship software, thanks to helping flag regressions quickly. Test-driven development. A subset of automated testing where tests are written before the actual code is. Code reviews. Before committing code, other engineers review and sign this off.

92
251
20
1,784
"React I Love You, But You're Bringing Me Down" marmelab.com/blog/2022/09/20…
The 2019 "Just use React" campaign against third-party state management libraries by the React core team is still the worst advice with the biggest impact I can think of It directly led to over-usage of Effects and Context in application code, where they absolutely do not belong
9
6
1
71
Kimmo Puputti retweeted
Gergely Orosz
@GergelyOrosz8 Jun 2022
RFCs / design docs is this very interesting part of software engineering, where there are two types of people: 1. Those who worked at a company where there was a culture of RFCs and have seen the benefits (and some tradeoffs) 2. Those who never did and assume it's useless.
Gergely Orosz
@GergelyOrosz19 May 2022
What are some good engineering planning docs (e.g. design docs, RFCs, ERDs, ADRs) that you've seen? What structure did they have? If you have examples to share - either as a comment or in DMs - even better.
21
38
4
352
Load more