!nonRant
First few days as a professional software engineer (c# .net) have gone decent. Made my first bigger commit today started working on a small new feature that requires more work.
CoWorkers are really nice, boss is cool, super chill over all. #feelsgood

"I found this tool that we should use because I'm a manager and its simple enough that my tiny little manager brain could set it up!"

Oh wow good for you, Mr. Manager! And what, praytell, does the tool require?

"All proprietary and cost-ineffecient products: MSSQL Server and Windows IIS! What do you mean we have to get the data out in order for it to be scalable? Look at it! I set up a website by clicking on an EXE i downloaded from github!"

Amazing, Mr. Manager. So you violated our security practices AND want to pocket even MORE of our budget?

Kindly fuck right off and start suggesting things instead of making people embarrass you into stoping your fight for your tool (has happened on more than one occassion).

I'm interviewing with the data architect in two weeks' time, a self-proclaimed ninja. The chap has done PL/SQL development on SQL Server 2008 according to his LinkedIn profile. Yeah, okaaay...

Well started on a support job about 1,5 years ago. Two days ago I had an interview about a new position in the same company, as a c# programmer. :)

I really hope I get it and I think I will. On Monday they will ask the rest of the crew what they think on the scrum meeting.

I'm just self taught on php so this will be fun. I hoped for this when a took the job, but I didn't think it would happen.

I have worked a lot with the development team the last year, with tests and I have also done some TSQL work so they all know some of my knowledge. But still I'm a little nervous.

Not a fan of legacy products which make use of a tonne of TSQL stored procedures, especially when they include a mess of logic, spelling errors, no version control of course, all squirreled away for some unlucky person to find and unpick in years to come.

In banking industry it brings up security concerns. We were in the exact same situation, however using SAS+SPDE with some custom SAS and tsql queries. Our database was merely 100TB, still it was a nightmare to assure stable performance thoroughly, because SPDE could not properly handle SMT. After having 24h++ daily flow processing times, the managers have decided to rent a 6 years old IBM power 7 with dedicated processor cores, which eventually have truncated the processing time down to 15 hours. This was a time limited contract, for 6 months. I've left the company in a short while, but this made the managers to rethink buying a more up to date server, so now the daily processing flows now are around 11,5h. Long story short, sometimes a little architecture optimization does the trick.

Why is it that in every other goddamn programming language if a function takes a parameter of string you can specify a variable but you have to create a goddamn composed string in t-sql for half the ddl and server functions because they expect string constants ????

And still
This has HAD to have been a complaint for a long time now !
Maybe I want to populate a json configuration file or a table with constants and values for things ?

I know that building a cmds text isn’t that much different but it does add extra annoyances and it really is something that should have been fixed 12 or more years ago in 2008 !

Why does the TSQL BETWEEN operator include the first and last value in the results when filtering on numbers, but only includes the first value and not the last for dates?