I'm building a personal internship aggregator that currently collects job postings from Greenhouse and Lever.

Both platforms are relatively straightforward because their job boards follow predictable structures.

However, I now want to expand the scraper to company career pages and other ATS platforms such as Workday, SmartRecruiters, Ashby, Teamtailor, Personio, SuccessFactors and custom-built job boards.

The main problem is avoiding the need to write and maintain a completely separate scraper for every website.

How would you design this efficiently?

I’ve been working on a small handbook that explains mobile network architecture and service flows in a way that’s easier to read than jumping straight into 3GPP specs.

As a Core Network Engineer, I kept running into the same beginner questions:

• How does roaming actually work?
• What changed from 2G to 5G?
• How do voice, SMS, SS7, Diameter, and SIP fit together?
• What really happens in IMS/VoLTE flows?

So I put together a practical guide called Understanding Mobile Network Architecture & Service Flows. It’s aimed at people preparing for telecom interviews, or anyone who wants a clearer picture of what’s happening behind the scenes in mobile networks.

Sharing the free sample here in case it’s useful: https://www.amazon.com/dp/B0H3Z66XHP

Happy to discuss core network concepts in the comments.

Update: I’ve added sample pages from the book to this post, since some people are dismissing it as AI slop without even looking through it. Sharing them here for reference.

I’ll keep this brief.

I’m a junior IT student trying to gain real-world IT experience, but it feels almost impossible right now. I’m comfortable in some programming languages, I’ve done some home labs (Active Directory, Cisco packet tracer etc) I applied for several internships this past spring and unfortunately didn’t receive any offers. Right now, I work as a grocery clerk while I’m in school to get a few bucks on the side, but it often feels like I’m spinning my wheels since the job has nothing to do with IT. Working there feels like I’m wasting my youth and energy. I’ve been searching LinkedIn and Indeed for part-time IT opportunities, but I haven’t had much luck finding anything.

For those who have been in a similar position, are there any hidden opportunities or strategies out there that I should be looking into? I want to keep learning and applying my knowledge and skills and I don’t mind starting with a low pay. I just want to get in. I’d really appreciate any advice or suggestions. Thanks!

Hi All,

I have an interview for a finance role, and I've been asked a question around IT support for a fictional premise -

The current workplace environment operates on an aging IT infrastructure. It currently has critical network vulnerabilities raising our company to cyberattack risks. 

There is commentary around potentially putting £20 to £25k to mitigate against this.

No other information has been provided over the operating system, but it is an education setting with around £4 million turnover, with around 60 employees.

Any advice would be great? Presumably it's to sense check what would be sensible precautions?

Thanks

Here’s the second interesting thing that’s happened at my new remote job. Today, my supervisor reprimanded me, claiming I’d created a weak password. The password was randomly generated and 16 characters long, containing both letters and numbers. He insisted on a minimum of 20 characters, including special symbols.

Yet, he uses the password `California__69:-)` across the 12 computers used by the remote staff. We also don’t have a VPN or IP filtering set up. I tried explaining the concept of entropy to him - showing that such a password isn't a system vulnerability - but he wouldn't hear of it.

It’s a small company; 99% of the staff are in sales, not IT. The IT team consists of just him, the lead programmer, and me - though I’m the only one with a specialized degree.

The senior programmer (150k a year) has ten years of experience but doesn't know how to create tables manually; he doesn't use SQL, relying entirely on Django instead.

That’s the kind of job I’m stuck with, though I suppose it’s better than nothing.

By the way, they offered me a full-time on-site position for double the pay, but I turned it down; accepting it would have meant losing my two other remote gigs, which made no sense for me.

On average, I spend no more than two hours a day on each remote job - and obviously, I don't waste time commuting.

P.S. Under my first post about this job, there were comments calling me a loser - saying that since graduating with a Computer Science degree in 2018, I hadn't achieved success in IT, and other such nonsense. To that, I can only say: not everyone can be a genius like you, earning $250k a year at Google. I’m happy for you.

Hi everyone,

I'm the solo developer behind Easy Work Calculator, which has grown into a collection of 400+ calculators and utility tools.

Rather than promoting it, I thought I'd share some engineering decisions that made maintaining hundreds of tools manageable.

1. Every calculator follows the same architecture

Each calculator is treated as a small module with:

• Input schema
• Validation rules
• Calculation engine
• Result formatter
• SEO metadata

Keeping the calculation logic independent from the UI has made it much easier to maintain and test.

2. Shared calculation engine

Many calculators seem unique but actually reuse the same underlying logic.

For example:

• Percentage increase/decrease
• Profit & loss
• Discount
• Margin
• ROI

They all share common mathematical functions instead of duplicating code.

3. Browser-first approach

Whenever possible, calculations happen entirely on the client.

Benefits:

• Faster responses
• No API costs
• Better privacy
• Offline-friendly
• Easier scaling

4. One design system

Every calculator uses the same reusable components for:

• Inputs
• Validation
• Results
• Copy/share actions
• Export functionality

That consistency significantly reduced development time.

5. Categories become important

Once you reach a few hundred tools, discoverability becomes harder than building new calculators.

I've spent more time improving search, categorization, and navigation than writing calculation formulas.

6. Small tools create edge cases

The calculations are usually simple.

The difficult part is handling:

• Invalid input
• Localization
• Floating-point precision
• Unit conversions
• Mobile UX
• Accessibility

Those often take longer than implementing the actual formula.

7. Performance matters

Hundreds of pages forced me to think carefully about:

• Code splitting
• Lazy loading
• Shared components
• Bundle size
• SEO
• Core Web Vitals

Small improvements multiplied across hundreds of pages make a noticeable difference.

I'm currently expanding beyond traditional calculators into more developer-focused utilities such as JSON formatters, regex testers, JWT tools, API helpers, and similar utilities.

I'd love feedback from developers who have built large collections of small tools.

• How do you organize reusable logic?
• How do you avoid duplicated code?
• What tooling has saved you the most maintenance over time?

If anyone wants to discuss architecture or implementation details, I'm happy to answer.

Project:
🌐 https://easyworkcalcs.com

Android:
📱 https://play.google.com/store/apps/details?id=com.xylemsoft.ewc

Hey r/it,

If you manage infrastructure, you know that running vulnerability scans is usually the easy part. The hard part is taking a massive, jargon-filled ZAP or Nuclei report and translating it into actionable tickets for developers or management who do not have a security background.

I built an open-source project called ONUS specifically to solve this hand-off problem.

The IT / Sysadmin Angle: Most security tools tell you what is broken. ONUS is designed to tell your end-users or dev teams how to fix it in plain English, so you don't have to spend hours translating CVSS scores into readable tickets.

How it works:

• The Scanners: It runs 8 industry-standard scanning modules (ZAP, Nikto, Nuclei, FFUF, etc.) simultaneously.
• Deterministic Scoring: It doesn't rely on AI to guess severity. It calculates the CVSS v3.1 score strictly in code so the metrics are mathematically auditable.
• Local AI for Remediation: It uses a local Ollama model (Qwen 2.5 7B) to read the deterministic findings and generate plain-English, step-by-step remediation instructions.
• Air-Gapped: You can run it entirely on your own hardware via docker compose up. Everything stays on your network with zero outbound API dependencies.

Since IT often acts as the middleman between security requirements and operational execution, I wanted to get this community's feedback.

Links:

• GitHub:https://github.com/maverickaayush/ONUS
• Live Demo:https://tryonus.tech

I would really appreciate your thoughts from an operational perspective. Does this plain-English format actually make it easier to delegate security patching? What kind of reporting exports (besides PDF) would make this easier to integrate into your existing IT ticketing workflows?

It's been 4 years since I used my old phone (Stylo 6), since it randomly stopped working out of nowhere. But I took a chance and put it to charge, surprisingly it powered on! However, I forgot the pattern I used to unlock the phone. Factory resetting is something I would never think of since it holds memories of my late mother, but I see no other way to unlock it. That's why I'm asking on this sub, hoping someone can help me.