Grzegorz Galezowski

3.7K posts

Grzegorz Galezowski banner
Grzegorz Galezowski

Grzegorz Galezowski

@GGalezowski

coder, OO designer, amateur guitar player and catholic dogmatic theology enthusiast. Author of free TDD book: https://t.co/ugwtQLYyT7

Kraków Katılım Haziran 2012
709 Takip Edilen447 Takipçiler
Grzegorz Galezowski retweetledi
Hassan Abedi 📚🌿🦉🪬
@unclebobmartin Think we need some more concrete measures. Feelings can be misleading. If AI-assisted coding improves people's productivity, it must show up in some numbers somewhere, I suppose
GIF
English
2
1
6
562
Grzegorz Galezowski
Grzegorz Galezowski@GGalezowski·
@AdamTornhill If used well, AI can make us understand more code quicker. Not sure why this is talked about so little.
English
0
0
0
16
Adam Tornhill
Adam Tornhill@AdamTornhill·
Accept that you’ll no longer know every line of code ...but make the ones you do read count!
English
1
0
3
298
Grzegorz Galezowski
Grzegorz Galezowski@GGalezowski·
@resharper Is it possible to bring own model to Junie or connect with e.g. Copilot subscription or is it only for Jetbrains provided models?
English
2
0
0
69
JetBrains ReSharper
JetBrains ReSharper@resharper·
ReSharper 2026.2 EAP 2 is available now. The Junie preview continues with bug fixes for the initial integration as we keep working toward a more open AI agent ecosystem in Visual Studio. Learn more: jb.gg/rs-junie-acp-i…
JetBrains ReSharper tweet media
English
1
0
4
706
JetBrains ReSharper
JetBrains ReSharper@resharper·
@GGalezowski Hi, Grzegorz! Could you please clarify what you mean by connecting Junie and AI Assistant? Junie gets activated with the first prompt in the AI Assistant chat tool window when selected as the agent of choice in the bottom left corner.
English
1
0
0
70
JetBrains ReSharper
JetBrains ReSharper@resharper·
ReSharper 2026.2 EAP 1 is out with some Big News! This preview introduces Junie, JetBrains’ LLM-agnostic AI agent, as the first step toward bringing more AI agents into Microsoft Visual Studio ⛓️‍💥 Learn more and give it a try: jb.gg/rs-junie-acp-i…
JetBrains ReSharper tweet media
English
2
3
7
4K
Grzegorz Galezowski
Grzegorz Galezowski@GGalezowski·
@plainionist The whole point is that these prompts are unclear to a degree. I could input the final correct code into the llm and ask it to echo it back, sure, but I am guessing this isn't how we view LLM's usefulness.
English
1
0
1
15
Seb
Seb@plainionist·
Hot take: Most LLM hallucinations are caused by unclear prompts and missing constraints 🤷‍♂️
English
178
13
181
16.5K
Grzegorz Galezowski
Grzegorz Galezowski@GGalezowski·
@vladikk apologies for calling out like this. I'm rereading Balancing Coupling and can't wrap my head around this sentence in the Model Coupling section (included in the screenshot is the question on which I am blocked). Is there something I am missing?
Grzegorz Galezowski tweet media
English
0
1
1
73
Grzegorz Galezowski
Grzegorz Galezowski@GGalezowski·
@AdamTornhill I found it a fast way to build a "something like that" software. Sometimes "something like that" is all that's needed, many times it's completely unacceptable as is.
English
0
0
0
25
Adam Tornhill
Adam Tornhill@AdamTornhill·
AI doesn’t make building software free. It makes building _some_ software relatively free.
English
1
0
1
215
Simon Brown
Simon Brown@simonbrown·
Short-term productivity gains and headcount reduction from AI, but at what future cost? It'll be interesting to watch... - Non-technical teams are now shipping production code - including “one person teams” with engineers, designers, and product managers all in one role
Brian Armstrong@brian_armstrong

This is an email I sent earlier today to all employees at Coinbase: Team, Today I’ve made the difficult decision to reduce the size of Coinbase by ~14%. I want to walk you through why we're doing this now, what it means for those affected, and how this positions us for the future. Why now Two forces are converging at the same time. We need to be front footed to respond to both. First, the market. Coinbase is well-capitalized, has diversified revenue streams, and is well-positioned to weather any storm. Crypto is also on the verge of the next wave of adoption, with stablecoins, prediction markets, tokenization, and more taking off. However, our business is still volatile from quarter to quarter. While we've managed through that cyclicality many times before and come out stronger on the other side, we’re currently in a down market and need to adjust our cost structure now so that we emerge from this period leaner, faster, and more efficient for our next phase of growth. Second, AI is changing how we work. Over the past year, I’ve watched engineers use AI to ship in days what used to take a team weeks. Non-technical teams are now shipping production code and many of our workflows are being automated. The pace of what's possible with a small, focused team has changed dramatically, and it's accelerating every day. All of this has led us to an inflection point, not just for Coinbase, but for every company. The biggest risk now is not taking action. We are adjusting early and deliberately to rebuild Coinbase to be lean, fast, and AI-native. We need to return to the speed and focus of our startup founding, with AI at our core. What this means To get there, we are not just reducing headcount and cutting costs, we’re fundamentally changing how we operate: rebuilding Coinbase as an intelligence, with humans around the edge aligning it. What does this mean in practice? - Fewer layers, faster decisions: We are flattening our org structure to 5 layers max below CEO/COO. Layers slow things down and create coordination tax. The future is small, high context teams that can move quickly. Leaders will own much more, with as many as 15+ direct reports. Fewer layers also means a leaner cost structure that is built to perform through all market cycles. - No pure managers: Every leader at Coinbase must also be a strong and active individual contributor. Managers should be like player-coaches, getting their hands dirty alongside their teams. - AI-native pods: We’ll be concentrating around AI-native talent who can manage fleets of agents to drive outsized impact. We’ll also be experimenting with reduced pod sizes, including “one person teams” with engineers, designers, and product managers all in one role. In short: AI is bringing a profound shift in how companies operate, and we’re reshaping Coinbase to lead in this new era. This is a new way of working, and we need to leverage AI across every facet of our jobs. To those who are affected I know there are real people behind these decisions — talented colleagues who have poured themselves into this company and our mission. To those of you who will be leaving: thank you. You’ve helped build Coinbase into what it is today, and I am sincerely grateful for everything you've done. All impacted team members will receive an email to their personal account in the next hour with more information, and an invitation to meet with an HRBP and a senior leader in your organization. Coinbase system access has been removed today. I know this feels sudden and harsh, but it is the only responsible choice given our duty to protect customer information. To those affected, we will be providing a comprehensive package to support you through this transition. US employees will receive a minimum of 16 weeks base pay (plus 2 weeks per year worked), their next equity vest, and 6 months of COBRA. Employees on a work visa will get extra transition support. Those outside of the US will receive similar support, based on local factors and subject to any consultation requirements. Coinbase prides itself on talent density. Our employees are among the most talented people in the world, and I have no doubt that your skills and experience will be highly sought after as you pursue your next chapters. How we move forward To the team that is staying, I know this is a difficult day. We’re saying goodbye to colleagues and friends you've been in the trenches with. But here’s what I want you to know as we move forward together: Over the past 13 years, we have weathered four crypto winters, gone public, and built the most trusted platform in our industry. We’ve made it this far by making hard decisions and by always staying focused on our mission. This time will be no different – nothing has changed about the long term outlook of our company or industry. And most importantly, our mission has never been more important for the world. Increasing economic freedom requires a new financial system, and we’re building it. The Coinbase that emerges from this will be more capable than ever to achieve our mission. Brian

English
9
2
36
6.4K
Mads Kristensen
Mads Kristensen@mkristensen·
Which commands in Visual Studio should Copilot be able to call? I’d personally love to see it invoke Format Document and Code Cleanup for a clean, deterministic fixup of the code it just wrote. What would you like to see?
English
27
3
38
6.5K
Seb
Seb@plainionist·
Serious question: Do you still recommend Clean Code to junior developers? 🤔
Seb tweet media
English
69
0
77
13.8K
Seb
Seb@plainionist·
@GGalezowski thx for sharing - i ll check it out 👍😉
English
1
0
1
7
Seb
Seb@plainionist·
Unpopular opinion: Unit tests rarely have long-term value 🤷‍♂️ They’re often too tightly coupled to design and implementation details. Refactoring breaks them - so they fail as a safety net. Acceptance tests do better. They keep a healthy distance from your internal design.
English
2
0
4
233
Seb
Seb@plainionist·
@GGalezowski I like my tests to be a safety net - but if I have to touch them every time I do some non-trivial refactoring they can't serve well as such a safety net 🤷‍♂️
English
1
0
1
14
Grzegorz Galezowski
Grzegorz Galezowski@GGalezowski·
@plainionist I don't treat the first one as inherently a problem. Tying tests to module boundaries is a good thing as long as I pick the boundaries consistent with those I care for in my design approach. Some design approaches care about objects & their interactions, some don't.
English
1
0
0
11
Seb
Seb@plainionist·
@GGalezowski From my experience there are 2 main reasons: many UTs map to single classes and so mimic the product design and many UTs are written after the product code is written and so mocks tend to mimic implementation details 🤷‍♂️
English
1
0
0
18
Grzegorz Galezowski
Grzegorz Galezowski@GGalezowski·
@plainionist If this happens often it sounds like a lack of symbiosis between design and testing approaches. Tests assume different properties of design than the implementer puts in.
English
1
0
1
15
Seb
Seb@plainionist·
Many UTs I have seen are testing single classes and use a lot of mocks 🤷‍♂️ Now if I refactor the class - split it in two - the UT is broken. If I refactor the implementation, chances are high that mocks are broken. These effects are inherent to unit tests. Acceptance tests typically don't have those issues
English
1
0
0
24
Grzegorz Galezowski
Grzegorz Galezowski@GGalezowski·
@plainionist So if a test is too coupled to implementation details of the tested boundary it's typically a badly written test or the boundary is badly designed. Not inherent to unit tests. UTs are typically criticized for testing at łevel where the design struggles to keep a lasting form. 🤔
English
1
0
2
16
Seb
Seb@plainionist·
@GGalezowski of the subject under test 😉
English
1
0
0
18
Grzegorz Galezowski
Grzegorz Galezowski@GGalezowski·
@vladikk are you maybe considering publishing some kind of workbook companion for the Balancing Coupling in Software Design book? I am rereading this book and I think I am getting the hang of the models, but could use more of curated examples on different abstraction levels.
English
1
1
2
98