One might think that computers do coding these days. But is that really it? Does it make code cheap, is it for free? A poem.
One might think that computers do coding these days. But is that really it? Does it make code cheap, is it for free? A poem.
In software engineering, new tools, libraries and approaches sweep in all the time. How much time we want to spend to renovate things, adapt the shiny new? There is value in building your own work on the boring stuff, the things that just work, do one thing and do it well. What is fancy today is likely future tech debt.
There is probably around one thousand three hundred thirty seven static site generators out there. So why build a new one? Because it could be a 300 lines of code only, all-in-one, swiss army knife, hackable one. Kind of.
Recently I was looking at a project and wanted to capture a number of code metrics to see how the project developed over time. It turns out some interesting metrics can easily be extracted with basic shell scripting.
In a recent dive into spring framework proxies I was searching for a way to access real objects behind a proxy. That was required to fix field injection in jerseys jersey-spring3 extension.
It turns out that this is easily possible through the Advised interface that gets added to spring bean proxies as a management interface.
The interface provides the method getTargetSource() that allows you to access the current proxy target source.
if (bean instanceof Advised) {
Object realTarget = ((Advised) bean).getTargetSource().getTarget();
inject(realTarget);
}
The above code does work for static proxy targets, only. It breaks if hot swapping or pooling is used because the target obtained may be different on each access.
Your application code should not use those internal interfaces, anyway. Your libraries may.