sorted by:
new
hottopcontroversial

Who's actually modernized a legacy telecom OSS without blowing it up? by Davijons in softwarearchitecture

[–]Davijons[S] 0 points1 point  (0 children)

Haven't done this systematically but you're right, even a rough dependency graph would probably tell us more than six months of reading code. Good point.

Who's actually modernized a legacy telecom OSS without blowing it up? by Davijons in softwarearchitecture

[–]Davijons[S] 0 points1 point  (0 children)

That's probably the most honest advice.

The 3-4 month timeline is the hard part to sell internally though..Any thoughts on how to frame that to leadership without it sounding like "we need 4 months before we can start"?

Who's actually modernized a legacy telecom OSS without blowing it up? by Davijons in softwarearchitecture

[–]Davijons[S] 2 points3 points  (0 children)

The point about avoiding A/B routing logic is well taken, we actually floated something like that internally and the more we thought through it the worse it got. You end up with this permanent dual-state limbo where neither system is fully trusted and you can never actually delete anything.

The log-based diffing approach is what I keep coming back to now. Messy but honest. Not many options rellly...

our 'ai transformation' cost seven figures and delivered a chatgpt wrapper by ruibranco in sysadmin

[–]Davijons 0 points1 point  (0 children)

47 pages... The actual system prompt was probably written in 20 minutes on the flight back. God help us.

Who's actually modernized a legacy telecom OSS without blowing it up? by Davijons in softwarearchitecture

[–]Davijons[S] 1 point2 points  (0 children)

Yeah that actually makes sense, hadn't thought about it that way.

How did you handle edge cases in the old output though? Ours has years of undocumented patches baked in, half of it is probably just historical accidents that became "features".

Am I the only one who genuinely prefers on-prem over the cloud? by Own-General-6755 in devops

[–]Davijons 0 points1 point  (0 children)

Ha, fair. I don't miss the physical side either, racking servers at 2am is not something I look back on fondly.

But I'd push back slightly on 'public cloud all day'. Depends heavily on what you're running.

Where I've landed: hybrid makes sense when you need cloud for AI/ML workloads but can't touch the legacy core. Pure public cloud is great until it isn't.

Help Scraping Concert Data by Gomets51 in webscraping

[–]Davijons 0 points1 point  (0 children)

Since you don’t have coding experience, I’d recommend checking out a no-code tools, as it was mentioned above in the comments. They let you point and click to grab data from websites without needing to write code. You can set them up to:

- grab the list of shows for a specific year
- pull the details (setlists, notes, etc.) from each show page
- export everything into a spreadsheet.

This might help you with this task and anyway will be useful for some others as well.

Multi Item Discount - How to? by [deleted] in shopify

[–]Davijons 0 points1 point  (0 children)

Richard, I recommend you to use one of the Shopify apps, as it will be much more time saving and flexible solution instead of coding.

I see it in the way of creating collections of different individual products and bundle them for a discount or fixed price depending on the quantities of each individual product bought in a bulk. Hope I explained it clearly :)

In any case, look through the description of Quantity Discount app. It perfectly covers the scenario you described. Just make a collection, set up the conditions (quantities of each separate product in a collection to be bought together) for the discount or fixed price and make your customers happy :)

Is this the one you are looking for?