Urban75 Home About Offline BrixtonBuzz Contact

Today I have mostly been using ${insert development technology here}

I have now moved from Excel and batch files to SQL server and Visual Studio. Going from having batch files creating text files to be parsed in excel to having vb script input directly into an SQL database was actually a lot easier than I thought it would be. Now I just need to create a front end to it and sort out error capturing.
 
I have now moved from Excel and batch files to SQL server and Visual Studio. Going from having batch files creating text files to be parsed in excel to having vb script input directly into an SQL database was actually a lot easier than I thought it would be. Now I just need to create a front end to it and sort out error capturing.
... and how hard can that be anyway...

*whistles innocently*
 
You know, really, this title should involve
Code:
${DEVELOPMENT_TECHNOLOGY}
or maybe
Code:
$(read -p "what development technology have you mostly been using? " DT; echo $DT)





yes I have been bash scripting
 
Last edited:
ohmyliver - Thanks for mentioning that, that's a REALLY great tool, just been building an API for our site, so that's super handy timing. Think I'll stump up the $10 as well.
 
Man, reading this thread kinda makes me miss programming, and yet it kind of scares me too. How do you all keep your skills current? My background was in large mainframe systems for a life and pensions company, where the humungous backend was COBOL (and a surprisingly large amount of ALGOL too), so the technology was kinda static, and it was the complexity of the business logic that was the challenge. I definitely couldn't keep up with you guys pace of change nowadays, and I'm not sure I could have even when I was 25 years younger...
 
Man, reading this thread kinda makes me miss programming, and yet it kind of scares me too. How do you all keep your skills current? My background was in large mainframe systems for a life and pensions company, where the humungous backend was COBOL (and a surprisingly large amount of ALGOL too), so the technology was kinda static, and it was the complexity of the business logic that was the challenge. I definitely couldn't keep up with you guys pace of change nowadays, and I'm not sure I could have even when I was 25 years younger...

Almost snap! I started with a massive pensions management system in Pascal.

Keeping current? It's weird but it almost happens by accident when you're working. You go "oh look, an easier/better way of doing what I normally do", check it out and get it going. ime.

There are SO many ways of doing everything nowdays that nobody can be expected to know them all.
 
There are SO many ways of doing everything nowdays that nobody can be expected to know them all.

I certainly get that impression :D That must present its own problems in terms of maintenance of legacy systems I suppose, although I guess legacy in what most of the folk in here are doing doesn't really mean "1970s"* and that's no bad thing.

* my old place had a handful of programs that dated back to 1968/69, but one of the grey-bearded-godlike-ones figured out that the only code in those programs that actually dated from that time was the first couple of IDENTIFICATION DIVISION statements, and some of the variable definitions. The oldest actual still-live code was from three or four years later. :thumbs:
 
Last edited:
I certainly get that impression :D That must present its own problems in terms of maintenance of legacy systems I suppose, although I guess legacy in what most of the folk in here are doing doesn't really mean "1970s"* and that's no bad thing.

* my old place had a handful of programs that dated back to 1968/69, but one of the grey-bearded-godlike-ones figured out that the only code in those programs that actually dated from that time was the first couple of IDENTIFICATION DIVISION statements. The oldest actual still-live code was from three or four years later. :thumbs:

Nowdays legacy can mean "what we did two years ago". Which is why people need to take a bit of care picking things that aren't just fads, but things that will be supported for a while. (I'm looking at you GWT :mad:)
 
Ime, working in a non tech firm that works with software companies, the expectation isn't that you'll know them all, but that you'll familiar enough with MVC frameworks that you can pick up a new syntax. They're not the same at all, but being able to switch between languages and work out the slightly different approaches is generally seen as the sign of a 'good' programmer - admittedly, this is startup skewed where you generally need to know a bit of everything, front end, back end, devops.
 
Unity 5 beta 13's new metal-roughness physically based standard shader, in conjunction with allegorithmic substance painter.
 
Lots of disk failures over the weekend. TIAMU LSI MegaCli. A truly dreadful piece of software with an inconsistent interface and a very flaky driver.
 
fogbat you presumably know http://www.theie8countdown.com/

I've been mostly using Charles (which is excellent, again I've actually stumped up the 34 or so quid to get a licence for it at home) to get google analytics tracking data from an Android app.

I do wish that the GA chrome plug in, and the remote developer google thing would work with apps in general, rather than just web pages, and apps that use webview. I also wish that the implementation of GA didn't send out the data in batches, as it's a pain in the arse to map out a user's progress, and then try and map that back to the responses being sent out, and that's before parsing the strings.
 
Last edited:
So I finally had a reason to learn and use bash. OMFG that's a non intuitive syntax.

And I've been generating diagrams with graphviz. Which is - as far as it goes - amazeballs.
 
Yesterday it was C# and I think it's going to be C# for a while now. First real go with it and I'm liking it. Very Java-like.

Weirdest bit is how my colleagues seem to hate open source. Other than log4net and nuint it just doesn't seem to be a 'thing' anyone trusts.
 
Back
Top Bottom