Sometimes I feel that I do a lot of work, but I don’t make much progress. Part of that is lockdown. (Part of it is dealing with the MICT SETA, which means I really didn’t make much progress.) And part of it is the need to remember one of life’s lessons:
Success requires hard work and perseverance.
There are many misconceptions about cybersecurity. Today I’m going to look at some of these myths. It’s a good reminder for all of us to check our thinking.
Modularization is a long overdue feature of Java. It has been a major challenge, and the effort has taken many years.
Some statistics claim that 90% of security breaches involve human error. That means human error is the biggest cyber security risk for your company.
The pandemic and remote working make this even more critical than before. There’s been a huge increase in attacks since the start of the pandemic. Working from home has a different set of risks. And your friendly IT support person is no longer a desk away.
You may have already used some of the text formatting classes and methods in Java, such as
String.format() and the
And then you move from Java 8 to Java 11, and you get unexpected results.
There is no comfort zone in our current Covid-centric reality.
We know life is uncertain, but we used to believe we could plan for the future. The pandemic proved us wrong.
That lack of certainty about the future has kept us off-balance. We all had to find ways to deal with the uncertainty. Some of us hoped that it would end soon and everything would go back to normal.
But it didn’t end soon and life hasn’t gone back to normal. Now that vaccinations are (almost) a reality, everyone is wondering:
“What will life post-Covid look like?”
Last week I wrote about some of the indicators that will tell us if our website has been compromised. This week I want to give you an overview of what to do if you have been hacked.
AOP Around Advice Example
Last week we implemented simple AOP using the Spring AOP
@Aspect annotation. I left out all the Spring container details because I just wanted to focus on the actual aspect code.
This week I’ll implement around advice using both Spring AOP and the JEE/EJB AOP using the Interceptor API.
Every industry has its own jargon. Jargon is terminology understood by people in a certain group – and often meaningless to anyone outside the group.
I think the IT industry is way ahead of other industries when it comes to jargon, buzzwords and weird acronyms. Perhaps that’s because IT changes faster than other industries. After all, when last did your accountant need a new term for double-entry accounting?
Last week I covered the concepts and terminology of aspect-oriented programming. As promised, this week I’ll illustrate the main AOP concepts with some code examples.
How we actually implement AOP programmatically will depend on the framework/container we’re using. There are many implementations, including AspectJ, JBoss AOP and Spring AOP.
For the sake of simplicity, I’ll use AspectJ annotated classes as used by the Spring AOP as the examples. If you use a different implementation, your code may be a little different.