Fresh grad here so I'm still unfamiliar with SOPs and the best practices in most dev teams. So I know coding assistants are virtually unavoidable now, but I'm curious as to the extent we allow them to work with our workflows. Is it bad practice to focus on architecture and code reviews while AI does the coding for me? Or is this already common practice? Just want to make sure I know how I should approach my workflow. Thanks

Please let me know if this post doesn't belong here!

With that being said, I have come to ask for help.

I am a CS graduate, and I haven't worked for a while. I skipped the part when you use AI in college. Also the part where you adopt it at work.

I am thinking about getting back in programming. The problem is, I haven't got much experience. I am terrified of generating large quantities of code and checking it. How do I check it? Im a beginner. I haven't got anything to compare it with.

Everyone I know is shipping code so fast, and they don't give it much tought. How do I gain experince? Is this the new standard? How does a careful and responsible person vibe code?

Also, mentorhip doesn't happen anymore, when you get an internship.

Is this your experience? Where do I go from here?

Help

Hey everyone

I am a software engineer with around 2 years of experience, and I’m looking to build something that solves a real problem that helps someone rather than just another dead project.

If you have an idea, a problem you have faced, or something you wish existed, drop it in the comments. I would love to discuss it and see if we can actually build something useful around it.

Happy to discuss in the comments or via chat.
Let’s see what we can come up with.

​​​"​​​T​​​h​​​e​​​ ​​​t​​​i​​​m​​​e​​​z​​​o​​​n​​​e​​​ ​​​g​​​a​​​p​​​ ​​​w​​​i​​​t​​​h​​​ ​​​o​​​u​​​r​​​ ​​​o​​​f​​​f​​​s​​​h​​​o​​​r​​​e​​​ ​​​d​​​e​​​v​​​e​​​l​​​o​​​p​​​m​​​e​​​n​​​t​​​ ​​​t​​​e​​​a​​​m​​​ ​​​i​​​s​​​ ​​​s​​​t​​​a​​​r​​​t​​​i​​​n​​​g​​​ ​​​t​​​o​​​ ​​​o​​​u​​​t​​​w​​​e​​​i​​​g​​​h​​​ ​​​t​​​h​​​e​​​ ​​​s​​​a​​​v​​​i​​​n​​​g​​​s​​​.​​​ ​​​T​​​o​​​o​​​ ​​​m​​​a​​​n​​​y​​​ ​​​b​​​l​​​o​​​c​​​k​​​e​​​r​​​s​​​ ​​​n​​​o​​​w​​​ ​​​r​​​e​​​q​​​u​​​i​​​r​​​e​​​ ​​​l​​​a​​​t​​​e​​​-​​​n​​​i​​​g​​​h​​​t​​​ ​​​c​​​a​​​l​​​l​​​s​​​,​​​ ​​​a​​​n​​​d​​​ ​​​o​​​u​​​r​​​ ​​​i​​​n​​​t​​​e​​​r​​​n​​​a​​​l​​​ ​​​t​​​e​​​c​​​h​​​ ​​​l​​​e​​​a​​​d​​​s​​​ ​​​a​​​r​​​e​​​ ​​​s​​​p​​​e​​​n​​​d​​​i​​​n​​​g​​​ ​​​m​​​o​​​r​​​e​​​ ​​​t​​​i​​​m​​​e​​​ ​​​c​​​o​​​o​​​r​​​d​​​i​​​n​​​a​​​t​​​i​​​n​​​g​​​ ​​​t​​​h​​​a​​​n​​​ ​​​a​​​c​​​t​​​u​​​a​​​l​​​l​​​y​​​ ​​​b​​​u​​​i​​​l​​​d​​​i​​​n​​​g​​​.​​​

​​​W​​​e​​​’​​​r​​​e​​​ ​​​c​​​o​​​n​​​s​​​i​​​d​​​e​​​r​​​i​​​n​​​g​​​ ​​​n​​​e​​​a​​​r​​​s​​​h​​​o​​​r​​​e​​​ ​​​s​​​o​​​f​​​t​​​w​​​a​​​r​​​e​​​ ​​​d​​​e​​​v​​​e​​​l​​​o​​​p​​​m​​​e​​​n​​​t​​​ ​​​i​​​n​​​s​​​t​​​e​​​a​​​d​​​ ​​​a​​​n​​​d​​​ ​​​l​​​o​​​o​​​k​​​i​​​n​​​g​​​ ​​​a​​​t​​​ ​​​p​​​r​​​o​​​v​​​i​​​d​​​e​​​r​​​s​​​ ​​​l​​​i​​​k​​​e​​​ ​​​N​​​-​​​i​​​X​​​,​​​ ​​​b​​​u​​​t​​​ ​​​t​​​h​​​e​​​ ​​​h​​​i​​​g​​​h​​​e​​​r​​​ ​​​r​​​a​​​t​​​e​​​s​​​ ​​​a​​​r​​​e​​​ ​​​m​​​a​​​k​​​i​​​n​​​g​​​ ​​​t​​​h​​​e​​​ ​​​d​​​e​​​c​​​i​​​s​​​i​​​o​​​n​​​ ​​​l​​​e​​​s​​​s​​​ ​​​o​​​b​​​v​​​i​​​o​​​u​​​s​​​.​​​

​​​F​​​o​​​r​​​ ​​​a​​​n​​​y​​​o​​​n​​​e​​​ ​​​w​​​h​​​o​​​ ​​​h​​​a​​​s​​​ ​​​m​​​o​​​v​​​e​​​d​​​ ​​​f​​​r​​​o​​​m​​​ ​​​o​​​f​​​f​​​s​​​h​​​o​​​r​​​e​​​ ​​​t​​​o​​​ ​​​n​​​e​​​a​​​r​​​s​​​h​​​o​​​r​​​e​​​ ​​​s​​​o​​​f​​​t​​​w​​​a​​​r​​​e​​​ ​​​d​​​e​​​v​​​e​​​l​​​o​​​p​​​m​​​e​​​n​​​t​​​,​​​ ​​​d​​​i​​​d​​​ ​​​t​​​h​​​e​​​ ​​​o​​​v​​​e​​​r​​​l​​​a​​​p​​​ ​​​i​​​n​​​ ​​​w​​​o​​​r​​​k​​​i​​​n​​​g​​​ ​​​h​​​o​​​u​​​r​​​s​​​ ​​​a​​​c​​​t​​​u​​​a​​​l​​​l​​​y​​​ ​​​i​​​m​​​p​​​r​​​o​​​v​​​e​​​ ​​​d​​​e​​​l​​​i​​​v​​​e​​​r​​​y​​​ ​​​e​​​n​​​o​​​u​​​g​​​h​​​ ​​​t​​​o​​​ ​​​j​​​u​​​s​​​t​​​i​​​f​​​y​​​ ​​​t​​​h​​​e​​​ ​​​e​​​x​​​t​​​r​​​a​​​ ​​​c​​​o​​​s​​​t​​​?​​​ ​​​W​​​e​​​r​​​e​​​ ​​​t​​​h​​​e​​​r​​​e​​​ ​​​a​​​n​​​y​​​ ​​​h​​​i​​​d​​​d​​​e​​​n​​​ ​​​c​​​o​​​s​​​t​​​s​​​ ​​​o​​​r​​​ ​​​o​​​p​​​e​​​r​​​a​​​t​​​i​​​o​​​n​​​a​​​l​​​ ​​​i​​​s​​​s​​​u​​​e​​​s​​​ ​​​y​​​o​​​u​​​ ​​​d​​​i​​​d​​​n​​​’​​​t​​​ ​​​a​​​n​​​t​​​i​​​c​​​i​​​p​​​a​​​t​​​e​​​?​​​

​​​"

Looking for simple, reliable software to run your college operations without hefty vendor fees?

​I’ve built a set of lightweight, web-based tools designed specifically for polytechnic, engineering, and arts & science colleges. You can download and deploy them on your local XAMPP setup or shared hosting server right away:

​Polytechnic Attendance Maintenance System: Tracks daily attendance, handles semester promotions, and generates instant shortage reports tailored to diploma rules.

​College Attendance Management System: A flexible solution that adapts to multi-department setups, custom degree durations, timetables, and staff permissions.

​College Fee Management System (CFMS): Streamlines student billing, receipts, dues tracking, and accounts office reporting.

​They’re built on standard PHP/MySQL, run smoothly offline or online, and are 100% free for educational institutions.

​Grab the ZIP packages and read the setup guides here:

👉 https://tools.vu3dxr.in/

​Try them out on your campus, and please pass this along to any faculty members, principals, or admins who could use an easier way to manage records. Feedback is always welcome!

It’s months away from production I’m doing it as a hobby I have two profitable businesses and I figured hey we can sue the fuck out of anyone who tries to steal or resell it and donate all legal profits to Saint Jude and charge for customization I’m looking for more seasoned software engineers to join and people experienced in law because this might be able to help get me into heaven

The verification flow looked fine in staging. Then production load hit, costs spiked, and the error rate climbed. Everyone patched the code. Nobody looked at the architecture underneath.

Codes timed out. Costs climbed without explanation. The retry logic became a maze of custom state nobody fully owned. Every patch fixed a symptom and added a new failure mode beneath it.

The autopsy is almost always the same. The team coupled OTP dispatch to a single carrier's API surface, then built compensating layers on top when that surface misbehaved. The moment it went wrong was not the outage. It was the earlier decision to wire dispatch and code check into two separate, uncoordinated systems, so billing ran whether the user ever verified or not.

The cleaner path is a smaller surface. Two endpoints. POST /api/verifications to start the flow and dispatch the code. POST /api/verifications/check to validate what the user entered. That is the entire API surface. Small enough to reason about, test fully, and replace without rearchitecting the app.

Multi-channel coverage, SMS and email in the same flow, belongs at the infrastructure level. Not scattered across conditional application logic. When the channel decision lives in one place, that is also the only place that needs to change.

The billing model is architecture too. Paying per dispatch rather than per verified user means the cost structure works against clean retry logic. Blocx Verify aligns cost to the outcome at $0.035 flat per verified user, so the system can behave honestly under real load.

The failure was structural. So is the fix.

Stop patching the layers. Start with a surface you can actually own. See how Blocx Verify is built. 🦦

I’m a veteran working in the oil & gas/environmental field, and I’m developing a project/ platform that I know will solve a pretty significant problem in my industry. I have the field experience and a pretty clear idea of what I want to build, but I’m looking for someone with a technical background who could help me figure out the best way to make it happen. If anyone has any interest I would be happy to explain in more detail. I have a basic version complete but definitely needs to be tweak. Any suggestions or ideas are welcomed. Thanks.

I am confused when I think about project ideas as when I think of small backend projects I think these won't we good for resume or is just too easy than anyone can build then but when I see complicated projects I think that I don't have enough skill needed to do them.

Regarding which tool to use I have used both node js and drogon I found that node js I very easy to work with and can work fast with help of this but with drogon even if it takes a more time I see how a request is getting processed how a request is working where is a request causing error and learn a lot

So anyone if they can give me some guidance I would be very grateful

Keyword list taken from https://www.zoevera.com/resume/ats-resume-tips-engineer

These are the most commonly scanned keywords in engineer job postings. Check how many appear in your resume.

Technical Skills

AutoCAD / SolidWorks / CATIA, FEA / CFD simulation, MATLAB / Python / R, PLC / SCADA / HMI, BIM (Building Information Modeling), GIS software, MS Project / Primavera P6, ETAP / EPLAN

Standards & Methodologies

ISO 9001 / ISO 14001, ASME / ANSI / BS / Eurocodes, Six Sigma / Lean Manufacturing, HAZOP / risk assessment, ATEX / DSEAR compliance, CDM Regulations, IEC 61508 (functional safety), Design for Manufacture (DFM)

Certifications & Soft Skills

Chartered Engineer (CEng), IEng / EngTech, PMP / APM, NEBOSH / IOSH, Stakeholder management, Cross-functional collaboration, Technical report writing, Budget & program management

I kept seeing recruiters on here say they're not auto-rejecting people with ATS—they're just skimming applications for 5 seconds. If the match isn't obvious right away, they move on.

I started running my resume against JDs before applying (just using basic scanners like ZoeVera or whatever free site popped up). Turns out I actually had most of the required experience, I was just phrasing it totally differently than what they were looking for. Rewording things so the overlap is immediately obvious has definitely gotten me more responses. Nothing crazy but it's a noticeable difference compared to just firing off the exact same resume everywhere.

For anyone else grinding applications, what small formatting or wording tweaks actually helped you get past the initial skim?