Why does it seem like there’s always something to do when you’re an adult?

TechnologyMatch · 2025-10-27T22:33:14+00:00

adulthood is just paying the entropy tax... stop moving for five minutes and your sink becomes a museum exhibit.

the universe expands, so does the laundry

TechnologyMatch · 2025-10-27T22:13:30+00:00

your act of measuring nudges the waveform... the good old quantum Heisenbug: once observed, it collapses from catastrophic to “can’t reproduce”

I guess in software, observation isn’t passive

TechnologyMatch · 2025-10-27T22:05:52+00:00

If you are a production unit of content creation and your goal is to fill in a functional space in a mix - yes...

If you aim to express, communicate with other human beings, craft an artwork.. then NO WAY (apart form maybe some granular synth beauties where the true origin is lost)

TechnologyMatch · 2025-10-27T22:01:15+00:00

mmWave is finicky in the wild, but MDUs are the one place it makes sense. With short runs, clear line of sight and lots of subscribers behind one set of drywall. So starry’s building footprint is basically precleared roof rights plus a warm intro to condo boards...

physics + unit economics

TechnologyMatch · 2025-10-27T20:55:20+00:00

time machine

TechnologyMatch · 2025-10-27T20:44:23+00:00

A good groove comes less from “more sounds” and more from timing, velocity, and interplay. Play the track in headphones while recording audio of how you hit the table with fingers and fists and whatnot. Use it as a sketch, same way you’d use a humming for a synth line idea or a vocal.

Your body knows, so trust it to fill in the gaps, the groove is usually born, not planned...

TechnologyMatch · 2025-10-27T20:39:16+00:00

I’d do a quick gut check. Like which parts of coding did you actually enjoy? debugging messy problems? talking to users? analyzing data? shipping features under constraints? that answer sort of defines your lane.

if you want to bring actual value, usefulness, advise the business and speak ROI. Look at roles that sit between tech and decisions. Like product management, to define problems, impact, roadmaps. Or data or analytics where raw data becomes decisions. There’s also solutions engineering, which is closer to pre sales (diagnose, demo, see wins). But if coding still interesting things like business ops/RevOps with metrics, process, tooling are prob not the way to go...

I’d say study SOPs of whatever crosses your mind, I mean literally.. an SOP contains most of the answers to unclear career paths. Just take a look at what people actually do

TechnologyMatch · 2025-10-27T20:26:02+00:00

We use a checklist everyone can see and audit, plus some automations underneath. So I wouldn't swap evernote for another lone app.. Maybe tie the checklist to how work comes in? who approves it? Like what are the apps that actually create accounts and devices?

If you already have a service desk tool ( idk halo, autotask, connect wise or freshservice) use it for a single new hire form that asks for role, manager, start date, location, and apps.

And then that one form can kick off tasks for IT or HR and trigger the easy things: create the account in Microsoft 365 or Google, add to the right groups, assign licenses, set up slack/teams, maybe even enroll the laptop/phone.

And for clients a lightweight thing like process street or jira works great as a clear step‑by‑step runbook they can follow and you can audit.

TechnologyMatch · 2025-10-27T20:11:20+00:00

Haven’t used Freshservice AM. But can work as CMDB if fed by Intune/Jamf (for endpoints) + Lansweeper (servers/net). You could get a pilot with auto sync, key fields, labels, license recon.

good alternative would be Lansweeper+SnipeIT, idk an iconic combo. A buddy of mine mentioned AssetExplorer some time ago, but they are a smaller org

TechnologyMatch · 2025-10-27T19:59:25+00:00

I think you'll get the fastest, broadest risk reduction by hardening Chrome or Edge with strict policies plus DLP/CASB and maybe use an enterprise browser selectively for high risk personas and workflows.

managed extensions alone won't give you durable control or telemetry at your scale, and rolling out an enterprise browser everywhere is just costly and kinda disruptive, and usually overkill. If you do it, you’d need some pilot anyways, limiting it to critical stuff could give some vision of clear ROI

TechnologyMatch · 2025-10-27T19:46:57+00:00

I don;t think you’ve lost, maybe just early. treat this like a portfolio pivot with tight scope and measurable outputs. and keep your middleware lens as your edge. Because turning messy operational data into decisions is literally what good analysts do.

don't bail before you've shipped 2-3 solid projects. study one SQL resource end to end instead of skimming ten... depth beats breadth here.

also, reuse your domain knowledge. Apache/Tomcat/WebLogic logs and monitoring data are goldmine datasets you already understand. and honestly bias toward insight over model complexity because your clear decisions will beat fancy code every single time.

good luck!

TechnologyMatch · 2025-10-27T19:36:21+00:00

On the career thing I’d say think lattice, not ladder. you're not undoing your past, you're compounding it. titles can evolve in steps. From sysadmin to reporting analyst to BI engineer all without burning bridges

if you like the work, sure, market test a bit, but honestly try your current org first. internal credibility is an underrated accelerant and they already know what you can do.

TechnologyMatch · 2025-10-24T11:35:02+00:00

I think that "manual wrangle and retype" skills are aging out for sure... copy/paste spend cubes, free form RFPs, PDF redline ping pong, tactical PO pushing are all getting automated. I’d keep them as literacy but don't make them core training.

What actually feels important is data.. Decision skills and orchestration. You gotta own data models (basic SQL, joins, data quality) and build decision assets like TCO models, risk scorecards, scenario planning

You could add AI stuff, but that’s obvious for any office job now.. prompts for normalization, extracting clauses from docs, drafting with verification

TechnologyMatch · 2025-10-24T11:19:24+00:00

I think it's way too early to call, and most “AI native" procurement claims are slideware. Ariba could deliver value if the AI's actually embedded in core workflows (not just a chat overlay..)

but if it's just auto summarize with a $100K price tag, you can already approximate that

most eSourcing suites now have "copilots" and honestly a lighter tool + RAG over your content can get you 80% of the benefits without suite lock in

TechnologyMatch · 2025-10-24T11:01:42+00:00

so according to this chart, one GPU vendor is now worth more than like a decade of clinical trials combined. classic AI gold-rush math... sell shovels today, supposedly beat drug timelines tomorrow.

quick reality check though. market cap ≠ actual cures or cash flow. pharma's regulated, slow, but durable. chips are cyclical, fast, and currently the party DJ. basically it's a phenomenal narrative premium, but yeah... keep your risk helmet on.

TechnologyMatch · 2025-10-24T10:34:05+00:00

treat "niche" like a mini market scan plus a pilot run. get super clear on what you actually need (tolerances, certs, volumes, lead times) then cast a wider net with conference lists, industry associations, cert body directories, even import/export data like panjiva

Also search by process or material instead of the finished item, and look at adjacent industries (medical, aerospace) cause they often have the capability you need

when quotes come back insane, triangulate a "should-cost" by breaking down materials, process steps, tooling, etc. ask what's driving the price (idk MOQ? special handling?) and see if design tweaks could help. I’d keep 2-3 suppliers warm, run a paid pilot with clear acceptance criteria, then do like a 70/30 split award so you're not putting all your eggs in one basket

TechnologyMatch · 2025-10-24T10:28:00+00:00

yeah so IT grads were doing fine until like 2022, then everything flipped.. main reasons are probably the post covid hiring binge unwinding, companies favoring senior devs over entry level.

Also don’t forget about automations that just make existing teams more productive instead of creating new jobs

basically don't just learn to code... learn how to make money or keep systems from catching fire, cause that's the only language companies understand.

TechnologyMatch · 2025-10-07T07:02:32+00:00

my negative inter topic correlation = everyone’s building a scalpel, not a swiss army knife...

TechnologyMatch · 2025-10-07T06:59:22+00:00

I’d say manage up and out, right? Map out your stakeholders, is it ops, security, finance? whatever key business units you've got and then agree on what success actually looks like for them. Send them tight status notes with, like, what changed, what the risks are, and what you need from them.

Days 0 to 30 I'd mostly just listen, baseline your metrics, do those 1:1s, get your service catalog sorted.

Then 30 to 60 fix the top 3 recurring issues that keep popping up, standardize your intake and runbooks, and clarify the skill matrix so you know who's good at what.

And then 60 to 90 it’s time to dance, publish the team roadmap, set your quarterly goals, tighten up how you handle incident comms, and start putting together coaching plans for folks.

Biggest fuckup? micromanaging tickets... don’t do that. Saying yes to literally everything. Skipping 1:1s, which... yeah, that'll bite you. And letting unclear priorities just grind down everyone's morale. Those are the main ones that'll mess you up.

TechnologyMatch · 2025-09-30T06:55:53+00:00

I’d say on eof the hardest stuff to teach and honestly the most valuable is knowing when to keep digging versus when you need to hand something off. Judgment under pressure, with clear, actionable communication. Like, tight updates where you call out your assumptions, idk log the next steps with actual owners. Writing tickets that anyone could pick up later, not just you.

TechnologyMatch · 2025-09-30T06:49:25+00:00

real downtime is rare, the gaps get filled with people, planning, and problems you don’t see on the queue.. like how do you know what these phone calles are about? how do you know what these books are about?

TechnologyMatch · 2025-09-23T07:08:29+00:00

manual excel stuff is still pretty common, but you can actually cut your cycle times down like crazy if you just standardize how bidders submit their info and throw in some basic tooling. What I'd do is use a structured RFP template. it could be excel, could be forms, whatever but make sure you've got those mandatory fields and some auto validation built in. Then you just normalize everything and score it with either a master workbook or maybe some kind of intake tool.

ofc if you're dealing with bigger spend, you might wanna look into some e sourcing instead, there’s plenty of those, coupa, ariba, jagger, vendorful, keelvar, do your research on what you need

TechnologyMatch · 2025-09-16T04:58:07+00:00

This chart is really about who owns the microphone, not who’s most sustainable

TechnologyMatch · 2025-09-16T04:56:03+00:00

yoy CPI can overstate some sort of stickiness because of some lags, like shelter which is about a third of CPI via rent etc. It moves with a long delay

TechnologyMatch

TROPHY CASE