What's Software Engineering

Hey y'all, so I'm getting into college soon, and I wanna have a way to be able to pay these students loans, do you think it's possible to find a job as a Software Engineer? I wouldn't say I'm that far into it, but I'm willing to do whatever it takes

Hi everyone,

I wrote an article about the impact of separating decision gathering from decision making in tech organizations. It discusses overcoming consensus paralysis and empowering team members.

Would love to get your thoughts and experiences on this approach!

https://www.sebastiansigl.com/posts/separating-decision-gathering-from-decision-making

Hi,

I currently work at a bigger tech company and my goal is to become a software engineer (.Net Developer) within the company.

My current role is not really technical and it's geared more towards customer service.

I have worked as a software developer on a very short contract after college two years ago and I feel that I still need more practice.

Since I would also like to serve, I thought that it would be a good idea to enlist in an MOS that would get me a TSC/SCI, and to then apply within the company for their cleared Software Engineering positions. I also understand that I'd most likely still need need to be sponsored for a polygraph.

If I don't get hired internally within the company, I would look for other Entry Level Developer roles that require a Top Secret Clearance. It seems like I'd have a better chance of landing a true Level 0 Entry Level Developer role with a Top Secret Security Clearance.

Overall, I'd feel more accomplished if I join the reserves instead of finding another way to get sponsored for a TSC/ SCI

I already know which branch I'd join and I'm good with the pros and cons of joining.

I have the following questions:

1.) Do you think this is a good idea?

2.) How and how long in advance should I tell my employer?

3.) Since I'm not really super skilled in software engineering yet, would it hurt me to take this detour? Should I use this time to continue to buld projects instead and should skip out on joining the reserves? Since I'll be working at the same company, I could also continue to study once I'm in the reserves.

4.) Based on some research that I've been doing, it appears that those with a TSC/SCI have a better chance of landing an entry level role with less experience/skill required, is that correct?

5.) Would companies care if my drilling station is out of state?

Any input would be highly appreciated

If you’re interested in trying it out it’s available on iOS! https://apps.apple.com/us/app/democrasee-io/id1623430660

Android is coming soon

Hi folks!

I’m wondering if there is a tool that will detect unused legacy code, methods, constants, components and files that are not used within the codebase? Using JavaScript

I did some web searching, I’ve tried depcheck but that is mostly for dependencies. Would appreciate any insight!

Hello, a friend of mine who lives in Romania is interested in working for a USA-based company.

Incentive is money.

He has 5~ years of experience developing mobile and desktop applications in .net and expertise in MAUI (his actual description was Mobile, Desktop, WPF, MAUI C# / .NET)

1. What is the process and hurdles for an eg Romanian to work for a US based company
2. What's the demand for his skillet in this market

Thank you guys!

Hello! I am doing a field research project that requires gathering information in a broad survey about my chosen career path -- computer programming. If you're interested in helping me out, please fill out this form!

https://forms.gle/npkiRZL5JTJRGDjM9

Thank you!

So, I recently interned at a huge product company. However, they didn't convert me into a full time employee :-) how difficult is it to get back to the company as a full time software engineer? (I am a fresher, not yet graduated).

https://preview.redd.it/zvz7qh970cyd1.png?width=585&format=png&auto=webp&s=5ad8022ef227098046e1666d1fd6175c26ed1be0

I would like to create my first saas, for fun. Is it worth to try it with a website Like linktree

Hello

I have a technical presentation coming up which will include various diagrams of my system. Stuff like the cloud infrastructure such as servers and Revit MQ and elastic search and databases and virtual machines and some backend stuff like how the APIs are called and what classes are responsible for what stuff etc.

Usually I just draw diagrams and draw.io but this is kind of an important presentation so I was looking for different tools which will make my diagrams look more professional and clean. I found dezyn.io but for some reason i cant download what i make there. It has very nice looking animations which shows moving data.

Ideally I would like something that has some animations to it or at least looks very nice and clean and something that can easily be added to google slides presentations.

Thanks!

I wonder if you go anemic or light DDD ? I use to go anemic with service class when i see i will look like a CRUD. But down the road, new requirements happen to be new business rule. And I am like : may be light DDD should be my go to architecture.

If you look at it, anemic is just aggregate root you stripped behaviour from.

Last job, some senior dev choose to go to anemic. We end up with DTOs for controllers, DTO for service, entities from repositories. Lot of transfer that made me think if they knew what they were doing.

I usually have one layer of DTOs that is shared by controllers and services. I don't usually go further than that.

But after some thinking, i wondering if light DDD should be favored instead of anemic models ?

At a previous job in my career, our process separated sprint work from operations and maintenance (O&M).

Sprint work was new features, O&M was for bugs that weren't designated as critical (those were just "all hands until it's done"). The process was that sprint work was always highest priority, O&M was for if you had time before the end of sprint or while things were being tested. We'd also deliberately underload some devs on sprint work so they'd have time to hit the O&M work.

O&M and sprint work also ultimately merged into different git branches, never to meet until the release sprint (the sprint dedicated to preparing for release).

I was pretty junior at the time and didn't fully comprehend why we did things this way. But it seems to fit with something my current manager wants.

Is this actually a good process, or are there showstopping flaws that young syresiv missed?

And is there a name for this specific process?

This is just from this closed QA in SO. IMHO reddit may be appropriate for opinion-based questions. If there is one more appropriate place to pose opinion-based questions, please tell me. Thanks in advance.

This problem is from p92 in this notes of SICP

Debugging techniques

...

introduce bugs on purpose to analyze results downstream

When googling I found one seemingly related comment sequence but that means we should not commit unnecessary known-buggy patches. That is not related with the above quote actually.

For this downstream definition, it seems to mean let forks to check bugs and report back to upstream. But that is one a bit weird action.

If using downstream service definition for the above, it seems to check whether downstream service will do something like signaling the error appropriately when with one bug. But what is the meaning of "analyze results" since if only to ensure error is thrown we have not much to analyze?

Q:

How to "introduce bugs on purpose to analyze results downstream", could you give some example based on the above definition 2 assumption?

(Edited based on close vote "Needs more focus" to use one definition explicitly. I am one newbie to programming. If you have problems with the above question, please tell me. Apologize for possible naive words above.)

Thanks for comments. IMHO HerbsterGoesBananas's reply is more appropriate here for the Therac-25 context. Anyway "The notes pdf doesn't say detailedly about the definition of downstream", so pampidu's is also fine.

I am frustrated with DRY being such a salient "principle" in Software Engineering literature. I have worked with several engineers (mostly mid to entry-level) that keep focusing on code duplication. They seem to believe that if they can reduce the amount of redundant code, then they can make the code base better. More often than not, I have seen this approach lead to poor abstractions that violate SRP and are not open for extension. I keep trying to tell my co-workers that some code duplication is okay. Especially if the classes are likely to diverge from one another throughout the lifetime of the code base. I can understand why people do this. It's much easier to get rid of duplicate code rather than write coherent abstractions that are testable and open for extension. I can understand duplication being valuable as a metric. I can understand treating reduced duplication as a side effect from focusing on what actually matters - writing code that can scale with the company, is testable, and that does not make your co-workers want to bash their head against a wall.

Am I crazy? What are your thoughts? Have you had similar struggles and if so, how have you addressed those?

Hello everyone! I hope you're doing well.

I was told that one of the rules of use case diagrams is that every actor should have at least one association with a use case, and no exceptions were mentioned.
What if the actor is a specialized actor (inherited from parent actor)? For example, actor A has two children, B and C. A is associated with some use cases, and so is B. Can C be there without being associated with any use cases?

I understand why it should be there - removing it will not reflect the requirements, and it IS associated with a use case through A. But I'm also under the impression that we can't have actors without any associations. Is this an exceptional case where we are allowed to "break" the rule?

Thank you and sorry if my question is stupid - I am trying to learn ^^

I heard this idea that even exception like DB connection failure, network exceptions should be represented in usecase scenarios. If so, how would they be translated in to activity diagrams or sequence diagrams.

This is in a academic setting and I know UML is not that heavily used in certain parts of the software industry. I'm asking for practical experience where this is applied irl.

I work at a mid-stage startup attempting a customized version of Ryan Singer’s ShapeUp framework.

I’ve seen this before: delivery slows down, someone introduces a new agile framework hoping it’ll fix everything, and they modify it so much it loses its original purpose.

Now, the team is stuck in a weird non-collaborative death-march cycle. Engineers are measured by the number of tickets they complete, which is ironic since ShapeUp specifically discourages breaking projects into endless tasks. Speed has overtaken quality, and morale is in the basement.

We’ve got one manager with 30 direct reports, an introverted CTO, a VP of engineering in Europe, and most of the team in South America, which makes everything complicated. Yes, frameworks are important, but these issues are about lack of leadership and experience IMHO.

Anyone else dealing with a similar silver bullet framework that’s been misapplied?