The Big Programming Thread - Page 502
Forum Index > General Forum |
Thread Rules 1. This is not a "do my homework for me" thread. If you have specific questions, ask, but don't post an assignment or homework problem and expect an exact solution. 2. No recruiting for your cockamamie projects (you won't replace facebook with 3 dudes you found on the internet and $20) 3. If you can't articulate why a language is bad, don't start slinging shit about it. Just remember that nothing is worse than making CSS IE6 compatible. 4. Use [code] tags to format code blocks. | ||
spinesheath
Germany8679 Posts
| ||
bakesale
United States187 Posts
On July 23 2014 23:57 MelChizm wrote: Yes Exactly, that is the result I am looking for. Here you go: > a ID Number 1 1 384835 2 2 435393 3 3 239493 > b ID 1 1 2 1 3 2 4 1 5 2 6 3 > b$Number <- a[b$ID, 2] > b ID Number 1 1 384835 2 1 384835 3 2 435393 4 1 384835 5 2 435393 6 3 239493 | ||
phar
United States1080 Posts
| ||
Manit0u
Poland17047 Posts
On July 24 2014 13:09 phar wrote: You might want to first ask why you need some parts of your code to know about the logging from other parts of your code. I think that's a good question. Usually you introduce logging for debugging and testing purposes. I don't think I've ever introduced code that would access the logs. Unless you consider saving object state logging... | ||
MelChizm
Netherlands15 Posts
On July 24 2014 06:26 bakesale wrote: Here you go: > a ID Number 1 1 384835 2 2 435393 3 3 239493 > b ID 1 1 2 1 3 2 4 1 5 2 6 3 > b$Number <- a[b$ID, 2] > b ID Number 1 1 384835 2 1 384835 3 2 435393 4 1 384835 5 2 435393 6 3 239493 tnx it works! | ||
boon2537
United States905 Posts
My first language is python, then I learned some C++ and made some basic data structure with it, and after that I mostly use java. And now, I'm making simple Unity game for fun in C#. To be more marketable, is it worth learning and getting good at C or should I just focus on C# and java? I feel besides optimizing systems, the benefit of being good at C is understanding low-level issues which most people wouldn't care. But, then again, I know nothing. What do you guys think about this? | ||
Manit0u
Poland17047 Posts
It's really a question of what direction you want to take. It's definitely easier to find a job in high-level languages just because there are more offers (depends on the language though, there will be more offers for Java than Haskell or Scala). If you're just starting out and not really sure what direction to take I'd stick with Java because it is very widely used (this includes both Java SE and EE, especially the Spring framework and Hibernate, they're required in almost every single Java job I've seen so far) and start moving towards Scala when you feel a bit more confident. This way you'll have more job offers to choose from and getting this first job is the most important (each next job comes easier). | ||
Nesserev
Belgium2760 Posts
| ||
berated-
United States1134 Posts
On July 25 2014 08:58 Nesserev wrote: I don't remember where I read it, but I really liked the logic behind a certain author's thinking. He basically said to stay away from Java if you want to be competitive and marketable. I'll try to paraphrase what he said as best as possible, basically, it came down to: And well, outside of getting a job... there's no real use for Java. There's almost always a language that'll do it "better". And well, you can always apply for a Java job without knowing Java... But let's get to the point: If you really want to be competitive and marketable, knowing a certain language probably won't help you get any further. Your code and experience will. Get some prestige projects going, show a wide variety of interests, and go deep in a couple of projects. Use the right languages for every project, don't just swiss-knife your projects with Java. For example: instead of using Unity and C# to make a game, why don't you pick up a simple media library, and code a game together from scratch, implement features like animations yourself?? I really don't understand anything about this post. At all. Don't learn the most sought after skill in programming? Don't learn a language that offers stable jobs than can pay $100000+. No use for java outside of the job? I suppose this conclusion is based on the fact that android is a fad. From as stupid as the author (or your interpretation of the author) tries to make all the one trick ponies out to be, why wouldn't you go into the sector of the field? Should be a piece of cake to walk in and wipe the floor with them, since they're just hobbyist. It also seems contradictory that so many one trick ponies leave no place to shine, but then state that knowing a language won't help on getting the job. How are the one trick ponies shining if they only know a single language and that doesn't matter? Maybe I'm just confused, is every person in this thread working for or applying to one of the biggest tech companies in the world? Personally, I think so much of what you should be doing should be about the specifics of what you want in life. Where do you want to live? Different areas have different language demands. What type of work is going to keep you engaged? Do you like web dev, game dev, mobile development? Do you want to work for a big company or small company? If these questions lead you to wanting to work for a company that needs you to do a lot of prep work to get hired, then you should definitely do so to give you the best chance. If all you want is a job, I'm thinking java isn't looking so shabby. | ||
berated-
United States1134 Posts
| ||
phar
United States1080 Posts
Also the idea that java programmers are one-trick ponies is ridiculous. Some of the best places to work in the world use java. * this may not be the case for some smaller companies, because they may just not have the time & manpower to spend getting someone up to speed | ||
broodbucket
Australia963 Posts
| ||
Ben...
Canada3485 Posts
On July 25 2014 12:06 phar wrote: Don't obsess too much about being dedicated to a given language. Just learn good practices, most of it will transfer between languages. Any (sufficiently large*) company that is at all honest about its hiring practices is not going to turn you away simply because you haven't been using their language of choice. You can pick up a new language without much problem. Three of my best co-workers had never used the language they're currently using before joining, it's not an issue. Also the idea that java programmers are one-trick ponies is ridiculous. Some of the best places to work in the world use java. * this may not be the case for some smaller companies, because they may just not have the time & manpower to spend getting someone up to speed This is what all of the more senior devs (a couple who do hiring included. Yay for programming forums that are mostly populated with older people) I've talked to have said. They would much rather have a smart junior dev that they can teach if need be that doesn't know a language but demonstrates good programming practices than find someone who is knowledgeable but is stubborn or could cause issues (of course being smart and being knowledgeable are two different things). One said in particular that the things he looks for most when hiring are that someone shows that they can learn (and is open-minded enough to learn, doesn't have too much of an ego to take criticism, will take advice, etc.), and that they are personable (he said if he could see himself going for drinks or lunch with the person). | ||
Nesserev
Belgium2760 Posts
| ||
Blisse
Canada3710 Posts
It's a bit different once you get a job, in that you can not be absolutely floored by the project but still enjoy the process, because while you're going to learn at a job, getting it done takes precedence, whereas with a project learning and having fun is the goal. tldr; learning a language is secondary to making something you're interested in. What you are interested in will narrow and essentially choose your choice of languages. If you want to build embedded systems, learn C. If you want to build Android apps or monolithic enterprise systems learn Java. If you want to build a game, choose what kind of game you want and what you want to learn, every language has the resources available for that, choose Unity if you care more about making games than programming games. If you want to go into Microsoft's stack or build .net applications, learn C#. And so on and so forth. However, if you want me to make a choice, I work at Microsoft so I'm going to say C# Java feels poorer in comparison | ||
Blisse
Canada3710 Posts
Also still wondering about this, http://blog.ploeh.dk/2010/02/03/ServiceLocatorisanAnti-Pattern/ I'm a bit confused as to what this guy is saying. The only thing that holds weight in my eyes is that your services are dependent on a service locator implementation and he doesn't even mention that. Do you guys understand/agree? | ||
boon2537
United States905 Posts
Thanks for the responses guys :D | ||
berated-
United States1134 Posts
It feels to me that the author is trying to use the service locator problem to solve the wrong problems. In the java world, using OSGi or JNDI appear to me to be implementations of the service locator problem -- both of which are extremely strong and necessary tools. This isn't to say that because I found an example that the pattern is amazing and should be used all the time. Like languages, patterns cannot be applied to every situation and a perfect outcome be expected. There are times that one pattern is going to be better suited than another. I do not understand the comments about intellisense or not knowing that you need dependencies. This feels to me to be more about good API design and documentation rather than a limitation of a pattern. If your library requires you to register something to a service locator, and then also register all of its dependencies...I'm starting to wonder what the point of hiding the service behind a locator is getting you. From my perspective, the service locator pattern feels to me more about the boundaries of accessing an external modules rather than hiding your own code from yourself. Let some other complicated service declare its own dependencies and its own implementation while still providing a service who can execute a contract. What's bizarre is if you read through the comments, the guy seems to be well spoken and know his stuff -- so I'm not sure as to why it feels like he's deliberately trolling on this post. | ||
nunez
Norway4003 Posts
need to change up my banana and coffee regime. | ||
Nesserev
Belgium2760 Posts
| ||
| ||