brd
Joined 15 years ago
Joined 15 years ago
Lemongrass is a SAP focused consultancy support customers as they look to keep up with SAP's "migration to the cloud".
We not so infrequently run into Frankenstein solutions built by our customers that need to be understood, cleaned up, and then potentially right sized or retired. If you enjoy and/or have experience rolling up your sleeves, diving into a poorly documented Kafka deployments, and coming out the other side the hero with crisp documentation in hand and a plan for longer term re-architecture activity, I've got the role for you.
If interested I'd love to talk to you, reach out to bdennett at lemongrasscloud.com
Being able to be bored and have those creative thoughts enter is for sure a useful thing. I'd argue the more important thing is being comfortable with silence/boredom. Being able to sit in a meeting and let awkward silence stew; or make a sales pitch and quietly let the gears turn, is a super power. If you're the one at the table better with silence, you have an inherent advantage.
Context: I'd put myself in the very low phone usage category but I still use my phone far more than I'd like. I pretty much just check email/text, HN, a bit of news, and occasionally doom scroll reddit. I'm also a developer turned exec/sales guy.
Fun fact: I still have my old pascal files on floppy disks in a box somewhere with a not so thin layer of dust on them.
Where stem/lem felt critical to successful NLP processing a few years ago, we've found stem/lem work to be much less important for downstream tasks when transformer based models are involved.
For topic extraction stem/lem still seems to do a lot to improve accuracy and for rules based approaches I can still see how it would facilitate more efficient processing at scale. I'd be curious to hear your experience fine tuning and/or training new models after stem/lem processing with transformers, we've admittedly done little testing to see how transformers actually performer if properly tuned to post-processed data.
Simple string matching isn't going to cut it, you really need a decent NLP based implementation. There should be weighing mechanisms to avoid bots surfacing stocks that don't actually represent the interest of WSB. The site should be crystal clear about the time period this is sourced from. And most importantly, please put a disclaimer about what it is, how it's working, and why it shouldn't be considered financial advice.
I appreciate that someone took the dive and then shared the process, pain and failure of seeing it through to its conclusion. The only thing missing is the attempt to raise VC money to scale it to some sort of expert system you can sell to enterprise customers.
There are different kinds of developers. At it's most base form, you have systems focused developers and algorithmic focused developers. Sure there is a grey area but I think those two buckets are pretty defensible.
In the data science world you have an exact parallel. Those who build the systems and those who optimize the thing the system supports.
In the ML world you have another parallel. Those who build the systems and those who optimize and pioneer the model architectures and parameters.
We never reached consensus on the titles for different kinds of developer/programmer/computer scientists. And we're failing now to reach consensus on sane titles for ML and DS.
One thing I wish we could find a solution to is our oil subsidy problem. I get that the US gov wants to subsidize oil for the sake of national security but those subsidies have all sorts of crazy unintended consequences. One of those consequences was that oil found a way to make itself the primary component of packaging.
brian dot dennett at gmail