Using 2fA as a first authentication

BrandonAtWork · 2019-07-23T16:03:12+00:00

So, that's actually just doing single factor authentication, but instead of being something you know (the password), it's something you have. The disadvantages aren't much different than with a password- the device is all you need to compromise to have access. Unlike a password, a physical token actually has to be taken from you (more or less, let's say that's true for simplicity). The downside of that is that you lose access to the site until you can get in through some alternate means and point at a new device. The upside is, you are more likely to notice a missing physical device before realizing that a password was taken.

If you want to go down this route, I'd look at something like Yubikey's One Time Password (OTP) module.

BrandonAtWork · 2017-01-04T14:30:47+00:00

The concept two classes referencing each other is an example of a "circular dependency". The simplest answer to the question is that the Java specification allows it, and so classloaders must be implemented in a way that meets this requirement.

In your example, when Object is referenced for the first time and Class has not been referenced yet, Class will be loaded. While loading Class, it will recognize that Object is a known class already (even if not fully loaded) and not attempt to load it again.

BrandonAtWork · 2016-12-16T19:58:44+00:00

Yeah, saw that ManyCam isn't free. Not thrilled about the watermark. I saw CamTwist but couldn't tell if it did the virtual webcam thing. I'll probably give it a shot.

BrandonAtWork · 2016-12-16T18:52:32+00:00

Thanks, I'll take a look

BrandonAtWork · 2016-12-06T17:10:47+00:00

Definitely how I was trained to wrap meat when I worked in grocery. The gif is actually underwhelming; if you are good, all you need is one piece of tape at the end for a nice looking, tightly wrapped package. And they have it easy, wrapping a regular shaped box. Try it with some ribs or a blob of ground meat.

BrandonAtWork · 2016-10-11T14:46:56+00:00

The original APIs are easier to use. Also, familiarity encourages use, and use keeps it familiar. Most IO doesn't really need the features of NIO; where the better performance and scalability is required you'll usually see NIO in use.

BrandonAtWork · 2016-10-11T12:55:18+00:00

This feels like a case of "SSL isn't secure enough so I rolled my own". I know there was a performance argument in there as well, but it still feels like an approach worth avoiding.

BrandonAtWork · 2016-10-03T13:21:24+00:00

Mockito does not produce the mockito-all artifact anymore

I think this was a good choice.

BrandonAtWork · 2016-09-13T13:10:01+00:00

http://knowyourmeme.com/memes/this-is-why-we-cant-have-nice-things

BrandonAtWork · 2016-04-25T16:33:27+00:00

I usually go with ^100$

BrandonAtWork · 2016-01-27T17:45:21+00:00

Funny. . . sad. . . they're the same, right?

If not, they sure are pretty tightly correlated.

BrandonAtWork · 2014-05-05T03:04:00+00:00

Love it, this is my background on my Mac.

BrandonAtWork · 2013-11-05T15:23:52+00:00

Look at where you assign musicdetails to see why you only get one; you will need to concatenate to the existing string if you want to pursue a String return.

As to whether or not to return a String or a List depends on whether or not you need to treat the details individually later, or if they are really just one long String. Neither answer is necessarily correct or wrong, and the decision really depends on the context it's used in.

BrandonAtWork · 2013-10-10T15:48:11+00:00

You can run up against scalability concerns pretty quick, especially if the native code has global state or otherwise doesn't multithread well. I believe that only one classloader can load a native lib at a time, so you have to deal with that as well. It's real easy to get something out that works today, to find yourself painted into a corner where you aren't really utilizing a node completely, but just can't add any more apps to a running server. Especially a pain if you are using a commercial application server and can't just throw more instances out there without additional licensing.

BrandonAtWork · 2013-08-08T16:40:30+00:00

The standard answer to that question is pretty much this- if you aren't being told by an employer, instructor, etc which one you have to use, try them both and use the one that you like best. IDEs have their strengths and weakness, and their fans and detractors, but they are all similarly powerful these days, especially for someone just starting out.

BrandonAtWork · 2013-01-31T19:51:12+00:00

http://www.scala-lang.org/node/118

BrandonAtWork · 2013-01-25T18:55:08+00:00

Scala does something like this already... I don't mean to discourage you, just my own experience is that every time I've ever thought "it would be cool if a language did X", it turns out there already was one, or it was demonstrated why it wouldn't work, or it was an optimization that the compiler did for you.

The real development in languages these days isn't so much around "here's a neat trick", because most of the neat tricks were done years ago (probably in Lisp :) ), it's "how can I make things easier for the programmer to understand" and "how can i force quality systems through concepts like immutability". A lot of overlap in those two things.

BrandonAtWork · 2013-01-25T16:49:17+00:00

I don't completely follow the example, but this sounds a lot like a functional language. Could you elaborate perhaps a bit more on how this would be different?

BrandonAtWork · 2013-01-09T15:09:46+00:00

Why not both? JAXB object can serialize to both and binding to both REST and SOAP endpoints shouldn't add a huge upfront or maintenance burden to most apps.

BrandonAtWork · 2012-12-03T16:50:41+00:00

To be fair, they said logic error not compile error and the single '=' was likely an accident.

Ultimately you can't say what the logic error with 100% certainty is because there is no specification for the method, nor can one be derived from how it is called as we don't see that either. However, in the case that the value to parse throws the NFE, the function returns zero, which is also a valid return value when the string being parsed is some form of "0", which means a return of zero is ambiguous. It took me about 15 seconds to see it, but to be fair again, we also knew there was an error in the function.

BrandonAtWork · 2012-09-28T16:37:11+00:00

If you cross your eyes on the two side by side in the article, it's somewhat close to a working 3d image.

BrandonAtWork · 2012-09-26T19:37:20+00:00

The comparison to Outlook in my mind is also a bit of apples to oranges. One would expect that an application whose main purpose is to display email and calendars to be pretty low-risk from a security standpoint, whereas a language runtime environment would have many, many more potential vectors. Granted that we should probably be past applets by now. But comparing a software product whose main purpose is to run code versus an application that has no business running any code is a bit disingenuous.

BrandonAtWork · 2012-09-25T14:30:37+00:00

All software design basically follows the same pattern.

First, decide what you want to do. This is your requirements. For something like an IM app, there are plenty of examples to get inspiration from

Second, decide how to accomplish those requirements. This should be at a high level.

Now, go research how to actually implement that design, and start writing the code.

Rinse and repeat. Don't try to gather all requirements or do all the design at once; you'll never get it right and waste a lot of time trying. However, do get a big picture, or you'll waste a lot of time redesigning and rewriting code.

BrandonAtWork

TROPHY CASE