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 1 year ago.
Improve this question
avoiding the obvious answer, "Maybe I shouldn't have been given this to work on."
Let's just assume I was given this as a complex 'test of my abilities to learn on the job'.
The app is using serverless framework and I understand the basics of the structure using AWS and where certain things go etc, but I am not used to the structure of the app i was given.
I have a folder for backend, app, and one for 'graph'. I would just like to know where to start? Is the suggested route to user 'serverless-offline' or being that I didn't design this app, should I go straight to plugging things into my AWS, and get it running that way? I know this is kind of a noob question, and regardless I'm just going to go ahead and start playing around with the two options, but I do have a small window of time to figure out how to get this running in a 'Dev' environment so I can give a quote on adding some new React things to the app.
Are you working for a consulting company that advertised you as an "expert" to a customer where you actually have a severe knowledge gap to even approach the project you've been put on?
If yes, you aren't going to get much more information here in a reasonable sized answer than you can easily find using a web search. In fact, your question is so vague that I personally think it's not answerable at all. So, get searching on your own, hopefully you can figure out enough stuff by the deadline that you/your company can "fake it until you make it".
If not, and you are an employee in a normal company, you should have some sort of knowledge transfer process in place where someone who is familiar with the application would tell you at least an overview of how it works and how to approach it for basic changes. Unless this person left the company and now there is nobody in house with the needed knowledge, which is your boss's/company's problem and - if they are a good company - they should give you a reasonable amount of time to figure out all of this stuff the hard way, in which case the answer is - again - get searching the web.
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 last year.
Improve this question
As the title suggests, I'm building a simple chat app in Node/Express + React, and I'm using socket.io to get real time updates.
However, other than the chatting itself, rest of my app is very basic (registering, signing in, creating rooms etc), and while it's definitely doable to make all those requests just socket emits, it feels like bit of an overkill.
So I was thinking of creating a regular REST API for that stuff and outsourcing it into a separate file, then creating another file just for the chatting function itself, where I'd use socket.io, but I'm afraid that it may seem a bit unprofessional, or leave an impression that I don't know how to use sockets well enough.
Key point: When finished, this app will be posted to my portfolio, so I'm not very concerned about what just "can work", but rather what's the best and cleanest way to do it? Should I switch everything to sockets and use them even for basic fetching of lists and stuff? Or is it better practice to mix the two, and use REST for, well, the rest?
In my experience, To mix the two is the best way to do that.
I did that in many projects and it worked well.
I surely think that modularity is the best way to make code clean and qualified.
So, to use both of regular REST API and websocket is more professional.
Thank you.
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 1 year ago.
Improve this question
If there is any PLC programmer or Twincat3 user out there. I would like to write my master thesis on Twincat3 in a company. Basically, They have different kinds of the Test bench, and they want someone to develop drivers for them. I have no experience with PLC or C++ or IEC61131 languages. Is it possible to learn any of these in 3 months, and then start writing the thesis? I have three months of Internship time before starting. I am having a bit of doubt. Even though it is daunting as an Electrical engineering student, I have no other options.
I thank you in Advance.
Also, The test benches are mainly Powerelectronics or Electrical machine test bench. I believe I need to automate the test processes in twincat3.
Best Regards
Good choice with TwinCAT 3. TwinCAT 3 is very capable, and quite easy to learn (of course dependent on your background, but generally a good platform to work on).
All I can support you with is a link to a TwinCAT 3 tutorial that I've created that is free of charge (available on YouTube):
https://www.youtube.com/playlist?list=PLimaF0nZKYHz3I3kFP4myaAYjmYk1SowO
There are also some other resources available both on YouTube and on the website. I've created a set of links here to help you find all the resources you might need.
To answer your question I would say it depends. Three months is not much time, especially considering you probably have a lot of other things that need to go in there (doing studies, writing the thesis, implementation, conclusions etc). It depends on the complexity of your project (it's not very specific what "writing drivers for them" means). If it's a simple project (including a very basic set of I/Os) it might be do-able. If it's anything more complex (like needing to add a front-end, doing motion control and maybe even safety) then it's most likely going to be hard to finish it in three months.
But again, I think more details on what you want to achieve is necessary.
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 1 year ago.
Improve this question
I just graduated and started my career as a junior software engineer. The one thing I am struggling with right now is not knowing when to stop doing something from scratch.
Last week I was told to simulate a warehouse environment and tell my boss what sorts of layout should be optimal. I spent days trying to build that in Simpy, Netlogo, Google OR tools. Even though I was aware there's a software tool called AnyLogic for doing all this for you, I just didn't use it.
After spending almost two weeks with partial development my boss wasn't satisfied with my work. And now I'm watching AnyLogic tutorials. I am not sure whether I should keep working on improving my partial work or switch to AnyLogic and save time.
I would highly appreciate if you give me some suggestions to know when to go for the built in stuff and when not to. I know it sounds very simple but it's actually not. Requirement analysis of a project is very tough.
Thank you. :D
If future flexibility (upgrading, knowing how it works, etc.) of doing it from scratch benefits you more than using a prebuilt system saves you time, do it from scratch. Otherwise it's not worth it. Time is money, and you can't get time back.
As long as you understand what exactly it is that you are doing with a prebuilt system then there is no issue in using it. When I code, am I doing something wrong by using VSCode instead of writing my own text editor? No, I know what a text editor does and how it does it.
When I use VSCode, am I doing something wrong by running it in Microsoft Windows or Linux, and not custom developing my own operating system? No, because I know what an operating system does.
The flexibility of writing my own software to do these tasks does not outweigh the time saved by using a prebuilt solution and therefore I will end up being more productive, and probably make more money in the end, by using them.
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 1 year ago.
Improve this question
I'm a 2nd-year student doing my bachelor's degree in Computer Applications. I'm really interested in becoming a Game Programmer and my dream is to work at Rockstar Games😅(it sounds a bit crazy). I'm really worried and I don't know how to program or write code. I'm an absolute beginner. Do you have any tips or advice on how to get there and fulfill my dream? Thanks😀.
I work as a gameplay programmer in Canada so here's a few thing I can tell you.
Best place to start is doing the tutorials on the Unity website. Make a few that interests you and see how you like that. Unity is used in a lot of studios and it's very easy to find a ton of resources online for it. Once your more comfortable with it i'd experiment with unreal also to get an idea for more than 1 engine. While doing all that the idea is for you to build a portfolio of games/projects you can show an employer. Its ez to make ios/android builds to have portable visuals. Game jams are a great place to hone in some skills. Most game jam even lets you join in alone so teams missing people can add you in(programmers are usualy whats missing the most).
For the game industry more or less any programming degree can do but every studio will make you pass a programming test. Knowledge of the engine they use be it Unity/Unreal will be very important. For bigger studios that use their own they look for good c++/c# knowledge an often more experience. At the momment the industry is in dire need of people so its def a good time to join.
If rockstar is your ultimate goal you can certainly try and apply there right away (there's no harm), but its often more difficult to get in via larger studios when you don't know anyone there (also knowing someone on the inside is a major plus anywhere). But even if you don't know anyone, smaller studios have a lot of opennings at the momment and will often give you a a chance. 3 to 5 years experience in is when most opportunities might open up. But again depending on the labour market place may be more desperate.
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 10 years ago.
Improve this question
I've been working on a small iPhone app that displays web content using the devices GPS context. I am hoping to list this application in the AppStore for free.
If I list the application under my name, does this create any considerable liability considerations?
Thanks in advance,
Ben
This is one of those questions that really belongs on a forum for IP lawyers. I'm not a lawyer, so this is somewhat speculative and should not be taken as legal advice.
A good rule of thumb is that anything you put in the public domain can open you up to legal liability. Whether you put your name on an application or not is irrelevant to whether or not you can be sued.
The open source people often include some boilerplate that amounts to "No express or implied warranty on this application, not even a promise that it will work and not brick your phone." How effective this boilerplate is would need a lawyer's perspective.
You appear to be in the USA, so the answer is "of course it does". And listing it in some other way also does. Anything you do, anywhere, at any time, that affects anyone in any way might well be taken as grounds for a lawsuit. If you want specific legal advice you should be talking to a lawyer.
IANAL, either. But if you give something away for free, something earnestly intended to help its users - and if you explain what it is, and whatever risks you're aware of - I don't think you have much to worry about. Certainly, you shouldn't. I say, do your best to make it good, safe, and all that, and set it free.