Comments for Bartek Szafko

Comment on Static keyword is the source of all evil, well almost by Bartłomiej Szafko

Bartłomiej Szafko — Wed, 07 Dec 2011 19:58:52 +0000

Yup typemock is the one i had on my mind. I didn’t know microsoft moles can do such kind of things

Comment on Static keyword is the source of all evil, well almost by Maciej Aniserowicz

Maciej Aniserowicz — Wed, 07 Dec 2011 13:59:49 +0000

Agreed 100%.

I know of 2 ways to mock such things: Typemock Isolator and Microsoft Moles. They basically intercept code being executed using profiler API. Nasty.

Comment on Static keyword is the source of all evil, well almost by xxjthxx

xxjthxx — Wed, 07 Dec 2011 10:51:03 +0000

You’re right. But doing withouth static constructs isn’t possible. There’s often some kind of point of entry which cannot be solved any other way than with static. Take ServiceLocator for example or any inversion control framework. The point of entry is static in such cases – implicit (via configuration) or explicit (via invoking static method).

BTW. Static constructs are often used out of laziness… but have you heard saying that a good programmer is a lazy one? Which may bring us to the conclusion that a good programmer is the one using static keyword .

Comment on Static keyword is the source of all evil, well almost by Damian

Damian — Wed, 07 Dec 2011 08:25:50 +0000

I would go one step further. My opinion is that there should never be static methods in your code, unless you have very strong argument behind it. Because of it you make tight coupling between two classes which using it, and as you truly said, you can almost forget about testability.

Extensions are very useful, however, because of their convenience there is a strong desire to put important logic there directly, and keep the state behind them anyway.

Comment on Static keyword is the source of all evil, well almost by skolima

skolima — Wed, 07 Dec 2011 07:05:43 +0000

It’s not ‘static’ itself that’s a major problem, it’s static methods or classes that are not stateless. That’s why extension methods are useful – they encourage stateless static behaviour.

Comment on Integrowanie systemów – komentarz by skolima

skolima — Tue, 08 Nov 2011 15:16:48 +0000

Baza danych wymaga, żeby systemy sobie ufały… To nie zawsze jest spełnione wymaganie, ba! Zazwyczaj jest to zły pomysł.

Z przykładów “specyfikacji”: dane są dostępne jako csv. Koniec specyfikacji. Napotkane wielokrotnie, w różnych systemach… Prośba o udostępnienie przykładowego pliku spotyka się z całkowitym niezrozumieniem. Przy czym zazwyczaj okazuje się, że c w “csv” pochodzi od “semicolon”, bo tak eksportuje dane Excel.

Zrobiona poprawnie integracja zawsze odbywa się za pomocą API. Przykłady tak różnych projektów jak Eclipse (OSGI), Amazon Cloud czy Facebook pokazują, że najlepszą metodą na utworzenie stabilnego i bezpiecznego połączenia między heterogenicznymi systemami (a także stymulowanie wzrostu ekosystemu daleko poza najśmielsze przypuszczenia pierwszego autora) jest po prostu stosowanie wewnętrznie tego samego API co udostępnione integratorom.

Comment on Dlaczego Entity Framework będzie rządzić światem by piotrbugla

piotrbugla — Sat, 08 Oct 2011 07:08:27 +0000

@iniside, a klucze obce masz założone na tabelach? Rozumiem, że tworzysz model ze struktury bazy.

Comment on Project Silk subjective review part 1 by Microsoft Makes the Case for More jQuery, Fewer Dependencies

Microsoft Makes the Case for More jQuery, Fewer Dependencies — Mon, 26 Sep 2011 20:11:06 +0000

[...] Silk best practices. One independent developer who definitely perceives this trend is Poland-based Bartek Szafko, who wrote last July, "When you look side by side on new Win8 shots and silk they look quite similar. I believe Silk [...]

Comment on Chroń swoje akcje w MVC by Bartek Szafko » Integrating WCF services with forms authentication

Bartek Szafko » Integrating WCF services with forms authentication — Sun, 25 Sep 2011 18:13:36 +0000

[...] and filters were implemented in MVC I used a PrincipalPermission attribute (more on this in blog post only in polish). PrincipalPermission is a standard System.Security mechanism to limit access to [...]

Comment on Project Silk subjective review part 2 no DDD, no CQRS and mighty handlers of doom by Bartłomiej Szafko

Bartłomiej Szafko — Wed, 07 Sep 2011 16:44:20 +0000

hmm, there are some nice examples on github by Szymon Pobiega