Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
Are SQL Developers and SQL Programmers same people? I have basic knowledge about SQL and want to improve it. plz help me?
No, I disagree - if you read Mike Gunderloy's excellent book Coder to Developer you'll understand a developer is a coder - but also a lot more.
A coder (= programmer) typically only writes code (possibly including unit tests) and that's about it. He usually gets a clear spec or task from someone else. A coder/programmer is more or less only concerned with writing, testing, and verifying code - nothing more.
A developer is a much more encompassing job description - a developer also deals with putting things into perspective, breaking up tasks into chunks that a coder can work on, he spends his time thinking about deployment and a lot more. A developer needs to know a lot more in his daily job than a coder.
Mike's book is good ... but if your going for a job the two terms SQL Programmer <-> SQL Developer are pretty much interchangable.
It just depends on what the hiring manager feels like calling the position.
Try SQL Exercises to improve your skills in SQL.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
So, I working on a problem at my workplace, that is a big company with a serious CNC shopfloor. Here I thought I could make the life much easier with a little software. I have the conception, I put a lot of work in it together with my helpful friends and here is the point, when I suppose to explain it to my leaders.
The problem is, I've never made anything like this before. So I don't know the way. I should use UML-diagrams and use cases, class diagrams etc? Or which is a preferred way?
Out of the management perspective you could explain why your programm is efficient and required to optimise the workflow. Creating a presentation could help you make the idea of the application clear and bring it in a form which is understandable.
If I were you I will go in priorities for activities diagram. You create an activity diagram of the old flow and another with the new flow. You show both to your manager and you compare them. Normally your program will minimise steps inside the new flow. Then you can say that with less steps to manage there will be more money to earn for your manager and you at the end :)
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I recently started looking at programming and have been quite interested in it. The only bad thing is that I don't know how code works, where I can write it, or what languages to take into consideration.
I want to learn how to make applications for the iOS operating system, and i heard Objective C is the language for that. Is Objective C something you would recommend to a beginner?
I just wish I could grasp the concept of programming a little better and get a better understanding because, as of right now, it seems extremely complicated.
As a beginning programmer, I would advise that you'd be better served learning how computers and programs work as a general concept, which will orient your thinking as to how programs are made.
I've heard lots of good things about the Haskell language in this regard, and I would recommend you start here: http://tryhaskell.org
Once you have a good concept of how programs work, and what kind of thinking and organisation is required, then you can move on to languages like C/Objective-C, which would be very frustrating to start on.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I recently started a new job in BI. I have done very well at adapting my T-SQL skills to working on a BI data warehouse. My problem is that the field is so diverse and the tools available are almost limitless, I dont know what to focus my research on. Can someone point me in the right direction? Im not looking for a "how to" but more best practice type of information. If you have worked in BI for several years where would you tell an entry level employee to start? What did you whish you knew when you started that you know now?
I constently feel like i have too many options and feel that if i dont pick the correct path that my work is useless...I bet someone else has experienced this when starting to work in BI.
I agree with Dan, starting with the tasks assigned. Do not search the internet for answers. Spend time reading books. By finding the solution in books, you learn a lot along the way. By googling your queries (which I'm sure must have been answered), you do not learn anything new.
Apart from that, you can start learning the basics of dimensional modelling, star schemas, snowflakes, slowly changing dimensions etc. Get used to these buzzwords. A good book to start can be Ralph Kimball's Datawarehouse Toolkit (http://www.amazon.com/The-Data-Warehouse-Toolkit-Dimensional/dp/0471200247)
Vijay
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I'm looking for some guidelines on writing a technical spec. This spec will be given to contract programmers for writing the business logic in an application. There is no user interaction in these applications, only application to application interaction. So far I've only been able to find information on writing specifications based on user input. I was thinking that maybe UML would be useful for this, but I'm not sure.
If anyone could point me in the right direction I would appreciate it. Thanks!
My suggestion is; if you doesn't have a lot of time to spend on this make some input/output sketches of the functions combined with UML flow diagrams. If you have time and some money to spend I can recomend "Object-oriented Modelling and Design with UML" by Michael Blaha and James Rumbaugh. read it and apply it on your requirements but instead of going to implementation leave it to the contract programmers. It is more time upfront but less questions later. Hope it helps.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I am currently my software engineering degree and as I am in my second year I need to select a topic for my project. I am totally confused on how to pick a good project topic, which I could use in my final year as well.
I have specialization in the following areas, java, vb.net, sql server 2005 as well as artificial intelligence.
I can also manage with designing interfaces for vb.net in flash.
Any help on a good topic which I should select would be greatly appreciated.
The best projects are the ones that you actually want to build. I struggle with this kind of thing myself in my "outside-of-work" projects.
Gauge the amount of time you have to work on it, that will probably limit your possibilities.
Pick something you're passionate about, even if it means learning a few (small) things -- this isn't a good time to learn C# or Ruby, but using learning how to use encryption in VB.NET is probably small enough.
If you can, build something you can use or that someone close to you can use.
An example:
I built a small P2P messaging client for my 3rd year security course which used Public Key encryption to send messages between clients. It wasn't fancy, but it worked and I managed to build it in about 3 weeks. A few of us used the client in class for the remainder of the term.