I write about topics in software engineering I’ve picked up as an Angular/C# Web developer.
Join my newsletter for weekly stories and development tips.
Finding working in large Visual Studio projects difficult? Try Working Files List – a free and easy to use extension that’ll help you keep track of your open files.
https://t.co/RR7JBtmGac
Creating mouseover/hover effects are a great way to add some interactivity/feedback to icons in your Web app.
Here's an intro to doing so with SVG images.
https://t.co/r5rn3meG3r
Maintaining duplicate code is tough.
We all try to follow DRY where applicable. But what if the "copies" aren't identical?
Depending on the use case, an interface could be the answer.
https://t.co/Mhv7QRpzmx
Ever wondered what unit test coverage is?
The latest edition of my newsletter gives an overview and tips on how to get started in C# for free.
https://t.co/ItE1JZRkFZ
@rogeriotaques If you're using .NET, you can use Visual Studio to debug remotely; I realise that's not much help if you're on a different stack though.
In any case, glad you got it sorted.
By using factory methods to create subjects in unit tests, you can balance tidiness with functionality, writing code for custom dependencies only in tests that need them.
@mjovanovictech Seems like a good approach to me.
Years ago, I did a side-project designed with unit tests in mind for the first time.
Some components were too small, some tests were a bit silly.
But the experience helped me refine my approach to both.
@catalinmpit Not quite as extreme as this, but I was once asked to whiteboard how I would redesign a company's system/infrastructure (using any technology available) if given the chance.
@alexhyettdev @GergelyOrosz I use a combination of command line and Git Extensions (on Windows).
As for Vim, some people swear by it, some people swear at it :)
wq = write (i.e. save), quit
q! = force quit
@dev_nishant28 @ThePracticalDev This is generally true.
But code design skill only counts for so much if product requirements come in bit-by-bit in each sprint/development cycle.
What seemed like the best abstraction at the time may no longer be true with a new requirement.
@bohlenlabs It's missing context for brevity:
Take that woman out (for dinner, etc)
Take that spider out (of the equation)
Another one to add to that list is 'bimonthly'. It's either every two months, or twice a month.
@andrewbaisden Writing tests encourages embracing SOLID and being function focused.
Code will be focused on a single objective, and functions offer a result to assert against.
One more suggestion: code to an interface (where applicable), rather than a concrete implementation.