A long time ago, I posted how I wanted to be able to use versioning in development of Paralycid. I was using Unity 4.x at that time, and to be honest, even though Asset Server was not being updated for a very long time, I liked it.
“Why not Git?” no one asked. Well, I believed that Asset Server was the best way for versioning if you are using Unity3D for your project. I turned a blind eye to its fundamental issues like the need of restarting Unity every time (and I did not complain at all because 32 bit editor was reaching limit of 2.5 GB resulting crash each time).
Ever needed to verify your text fields and/or text areas that the input is in correct form?
Well, I did. As a matter of fact, where I work right now demanded me to provide verification for the project we were working for.
I searched for any reliable verification libraries for Java, and in fact I found a few, most popular being from JGoodies but due to requirements I ended up writing my own using the way provided here. Then again, that way was not enough, lacking in a few ways, making me improvise on it, and here it is.
For anyone interested, it’s on my BitBucket account. I think code is very simple, and the Test class I provided gives a very clear idea as how to use it, or how to implement new validation ways. In any case, I will probably provide new examples and step by step implementation of a new verifier. All in all, I relied on the native method
setInputVerifier( new myCustomInputVerifier()); so it is pretty convenient to use. Where I work will use this library (not as it is though) in our other project, so I guess it will be useful to some of you.
Since the rise of web applications, abstraction levels has become nearly impossible to trace. For smaller teams with limited time and resources ORM, high level abstraction and deployability is important, yeah; but until when?
I’ve started to work at another software company two months ago. I had to quit my job at an R&D company I worked before as the head of software department at the end of May; but being an indie game developer and independent author, without a certain income nothing was going to work for me (and it didn’t, a rough couple of months), so I searched for a job and finally a colleague presented me where he works, where I have been working for two months now.
Using Grails, (built on Groovy, which is built on Java, which is built on…) ORM is inevitable, also you tend to overlook many things as deadlines and other issues are pushing. In the end, as a relatively new developer, issues that were assigned to me (respond times, load tests, other problems), I had no idea how to investigate (trace the problem to its core) since I am so used to use JDBC as most sophisticated bridge and Java as the highest level language. You may see why in various discussions on the net, especially here in this particular StackOverflow question.