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
So, imagine a person that likes math/physics/engineering problems. He also likes science and programming. Let's call him D.
D is in his mid-twenties, has much to learn about life and programming. He has the most experience in Pascal, C++, C, Python, Javascript. He also peaked into web development tools a bit. Note that, D is very enthusiast about solving & programming math/physics driven problems and can not imagine his job to completely lack such problems.
Now D got a really interesting offer to become a full stack engineer. The only concern is, that he is completely unfamiliar with this part of the development world. D likes the offer, but does not know how much math/physics, if any, is included in an everyday life of a full stack engineer. Is that none at all? Some? Or does it depend on the project? Could it be the most desirable knowledge in some cases?
Anyway D does not have the answers to any of the questions and is therefore having trouble accepting/denying the given offer. He is afraid that the lack of scientific approach in full stack development could bore him to death.
What do you think? I know people that are really good full stack engineers but bad (or none) math/physics knowledge. But I don't know any that good mathematician/physicist to go for a full stack engineering career. Can you help D?
The most helpful tip for D:
D should not make a Full Stack Developer career if he is afraid that the lack of scientific approach in full stack development could bore him to death.
Because, most probably it will do even if the project is somehow science-related. It is a rare case when a FSD will be loaded with interesting math/physics driven problems.
Better to find C++ or python positions with relevant specialization. Perhaps the most of relevant vacations that will make D happy are located in GameDev area.
P.S. Math/Physics related problems and Scientific Approach are different things =)
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 2 years ago.
Improve this question
Markus Malessa has provided some fantastic answers to Goole App Maker questions here on Stack Overflow. However, App Maker will soon be decommissioned. What will be the preferred alternative for App Maker experts like Markus?
I appreciate the call out although I would not necessarily consider myself an ‘expert’ by any means. I do have to say that the initial choice for AM was largely due to the fact that it was part of our G Suite subscription and I was somewhat familiar with Google Apps Script and HTML/CSS due to some free standing app development using the HtmlService. Given that my background and education is actually not programming related at all I would consider myself to be the target market for these types of programs were little to no code is required.
Unfortunately the reality is that my place of work never really committed much funding to this project outside of my time and more so this was probably what some coders would apparently refer to as their 20% project. So really at the moment I am not sure yet where I will end up after this. I’m afraid though that unless we decide to pony up some funds for something else we will be back where we used to be before this without a lot of functionality.
Anyway best of luck to all citizen developers that took a plunge into App Maker, you guys are all great and it has been a pleasure providing feedback to you all.
I recommend using Angular, since it's also based on JavaScript.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
Is there a legitimate reason why the majority of society (beyond CS-educated persons) should know about the abstractions we become familiar with in CS/programming (such as data abstractions, computer systems abstractions, etc)? Or does it truly not really matter to anyone but programmers, scientists, and engineers?
There is absolutely no reason why the majority of society should know about CS concepts. This is not the way society works, IMO. To be honest, a much stronger case could be made why the majority of the people should know about first aid then about CS.
There are a lot of professions out there which are crucial to maintain the standard of living we have now. Computer science is one of them, I'll give you that, so are doctors, engineers, mechanics, teachers,...
The majority of the people already know how to use computers because it's useful to them. Just like you know how to live in your house, you probably don't know how to build one from the ground up.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 12 years ago.
Improve this question
I have a quite big development experience and I wonder is it possible to start learning math from scratch. I forgot almost everything I know, even school program. Please give me some guidance on this. Where to start what to do. Are there any math books for developers. May be with exercises to write code or experiment, etc...
Any help is appreciated.
Yes, there are math books for developers:
Concrete Mathematics: A Foundation for Computer Science
Discrete Mathematics and Its Applications
It's hard to say if either one would be a good starting point without knowing what level you're at.
Assuming you have had high school math, I strongly recommend:
Concrete Mathematics, Second Edition
by Ronald L. Graham, Donald E. Knuth, and Oren Patashnik (Reading, Massachusetts: Addison-Wesley, 1994), xiii+657pp.
ISBN 0-201-55802-5
I'd review what you should know first (at least a little) before going on to new material. You'll need a good foundation in algebra, and at least some exposure to calculus before trying Concrete Mathematics or even The Art of Computer Programming.
If you want to go from the practical side of computing Robert Sedegwick, has written some books that have source code explaining computer algorithms and theory.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 8 years ago.
Locked. This question and its answers are locked because the question is off-topic but has historical significance. It is not currently accepting new answers or interactions.
I'm thinking of forming a Hackers Club at work. My idea is that we would meet monthly and at each meeting one member would present an interesting hack he had created. (The hacks presented wouldn't necessarily have to be software hacks; they could also be the sort of things you read about in MAKE magazine.)
There would also be ANSI standard pizza, veggie pizza, and beer and pop available for socializing afterward. I'm even thinking of calling the club "TMRC" even though it will have nothing to do with model railroads.
Has anyone ever tried doing something like this or have any advice?
We do this at the office. I call it 'Developer Fight Club'
Usually do challenges of varying difficulty and compete against one another.
At the end of it, we go over our solutions, do code-reviews and discussions, and then use either benchmark results or other people as the deciding factor for who wins.
Typically, the loser has to buy lunch for the winner :)
For ideas of things to do, try stuff from Top Coder, programming questions on Stack Overflow, or even simple "crackme" applications available on different programming sites.
The main rules you'll need to adhere to are:
Make It Fun
Make It Educational Make
Make It Fair
Try to rotate the challenges, so either everyone is really good at the subject, equally bad, or at least mix it up often enough that it doesn't favor one person's skillset too much.
If there are women in your 'hacker' group, consider the advice given in the Howto Encourage Women in Linux. Especially the 'meeting places and times' section.
This is a little beyond what you asked, but there is good info on how to plan for hackers and how to resolve issues among members in a polite, hackerly manner.
Overview:
http://events.ccc.de/congress/2007/Fahrplan/events/2133.en.html
Videos:
http://chaosradio.ccc.de/23c3_m4v_1500.html
http://chaosradio.ccc.de/24c3_m4v_2133.html
My favorite is the Tuesday Pattern:
If there's a scheduling conflict such that no day of the week is good for everybody, just hold the event on Tuesday. No exceptions! Simple and fair :-)
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 3 years ago.
Improve this question
I've been reading about Ocaml's consistent speed, rapid prototyping ability, and excellent memory management, and decided to take it up.
As I've already got Ruby, *lisp, Haskell, and Erlang under my belt, I'm interested specifically in what KISS-violating features I should look out for in Ocaml.
If you've started Ocaml with a background in the above languages, what was the most frustrating thing to grok? How did you get around this difficulty? What analogies helped you get into the flow of the language?
I'd also be interested in knowing whether you have done more than simply learn Ocaml, and have actually converted to it for a large percentage of your coding problems.
I found an excellent resource on Ocaml and its relation to most other languages: http://www.soton.ac.uk/~fangohr/software/ocamltutorial/lecture1.html
Not only does it explain the why, it also explains many of the little quirks likely to snag you as you begin.
Ah, I found a cheatsheet highlighting almost all of its syntactic weirdnesses.
I have heard the APress Practical OCaml is awful as well.
Introduction to Objective Caml is excellent and specifically addresses a few anti-KISS gotchas, such as ways the type-system can be unforgiving.
Coming to OCaml from a C++ background, I found replacing classes with variant types to be the hardest transition (and it was easy!).
There is a book about Ocaml "Practical Ocaml" it's not a really good book, but at least for getting started it's good enough. It's a quite practical language, which unfortunatly a "strange" syntax. If you like to see some "real" Ocaml then just look at the Shootout pages.
Regards
Friedrich