What do computer science engineers do?

  • Thread starter Thread starter geekynerd
  • Start date Start date
Click For Summary

Discussion Overview

The discussion revolves around the experiences and expectations of first-year computer science students regarding their future careers in the field. Participants explore the types of work computer science engineers do, the skills they are learning, and the challenges they face in understanding their career paths.

Discussion Character

  • Exploratory
  • Debate/contested
  • Conceptual clarification

Main Points Raised

  • One participant expresses uncertainty about their future career in computer science and seeks guidance on how to apply their learning in programming languages like C and Python.
  • Another participant suggests reaching out to working engineers to gain insights into their roles.
  • Some participants reflect on their own experiences, noting that the field offers a wide range of possibilities but also caution about the potential for ending up in an area that may not be enjoyable.
  • There are mentions of specific tasks and projects that computer engineers might undertake, such as writing scripts for configuration management and optimizing performance of applications.
  • One participant questions the motivations of those entering the field, suggesting that passion for programming may influence success.
  • Another participant humorously notes that a common task in the field is fixing bugs left by others, acknowledging this as a prevalent experience.
  • Some participants recommend seeking internships or networking with alumni to better understand the profession.

Areas of Agreement / Disagreement

Participants express a mix of agreement and disagreement regarding the motivations for entering the field and the nature of the work. There is no consensus on the best approach for the original poster to take in navigating their career path.

Contextual Notes

Participants highlight the variability in experiences and the importance of personal motivation in the field, but there are no definitive conclusions about the best practices for success in computer science careers.

  • #61
sbrothy said:
That's what I think I'm doing.

Yes, it looks like it.

sbrothy said:
I tried the PHP recommended way of just calling "session_start()" at the start of each page, but that didn't seem to work,

session_start must be called before any output is sent. It seems like you are unintentionally sending multiple byte order marks (and should not be sending any - they are invalid in XHTML and unnecessary in plain HTML) as well as comment tags before the DOCTYPE declaration.

Do yourself a favour and switch to HTML 5.

sbrothy said:
so now I'm handling the session manually.

Are you sure - I can still see that PHPSESSID cookie?

sbrothy said:
I still need to encrypt stuff

What stuff do you need to encrypt?

sbrothy said:
and use htmlspecialchars correctly.

Use a template engine like Twigg to avoid unescaped HTML.

sbrothy said:
I'm probably open for an SQL injection attack.

Use PDO prepared statements (or a database abstraction library like ADODb) to avoid this.

sbrothy said:
So if you have any more papers I'd love if you provide me with links.

No papers needed, this stuff is just PHP 101.
 
  • Informative
Likes   Reactions: sbrothy
Physics news on Phys.org
  • #62
Yeah, I'm new to PHP. I've used Perl before but mostly Apache (or Tomcat) and WebSphere App Server with Java. And C# and the whole Windows methodology. I appreciate your (relentless :smile:) advice. :smile:

EDIT: I meant JSP and JavaBeans.
 
  • #63
What I want to encrypt are the users passwords when I get registration going. BTW, you can't judge from my GIT link. It's hopelessly outdated. But yeah, I'm a noob here. Again I appreciate your input. No matter how hard the tone. I just have to swallow my pride.

EDIT: Oh sorry. I already said that about the version control.
 
  • #64
geekynerd said:
i work on a project where i build a app for my gymnasium in our college and my role is frontend dev and i have a teammate. we do code in flutter. sometimes i have some important classes and i will go to attend it in that time he will push something in my branch and call it a update. he will change so many files like i am hit with almost 100 of merge confict. by that i can confirm it is not fun working with someone. but the ui part it still fun working with ui. you just draw and design no complications unlike the backend engineer who will freak out how how they conna worute logic how they gonna design table.
He/She should at least check files in with informational comments and leave comments in the code. If he/she doen't it's bad discipline.
 

Similar threads

  • · Replies 18 ·
Replies
18
Views
7K
  • · Replies 30 ·
2
Replies
30
Views
5K
Replies
4
Views
3K
  • · Replies 14 ·
Replies
14
Views
4K
  • · Replies 7 ·
Replies
7
Views
3K
  • · Replies 8 ·
Replies
8
Views
3K
  • · Replies 3 ·
Replies
3
Views
5K
  • · Replies 3 ·
Replies
3
Views
2K
  • · Replies 3 ·
Replies
3
Views
3K
  • · Replies 21 ·
Replies
21
Views
3K