HN user

inSenCite

308 karma

I'm an engineer with a background in operations research and 10 years of engineering large scale operational change. www.rachitshankar.com

Posts6
Comments80
View on HN

I'm building a perp funding arbitrage aggregator. Aggregates funding rates across a number of DEXs to help users track down the most lucrative opportunities.

If there is uptake the plan is to build out a toolset to help with managing a portfolio of arbs.

As a python/stats focused dev, I just want a web framework that simplifies the idea -> website process.

I've been able to 'release' some simple tools into the public with plotly/django, but having to also then figure out things like gunicorn, dbms, vps hosting etc. is quite time consuming.

My biggest issue is that a lot of these frameworks seem to add complexity (under the guise of simplicity) as opposed to making things simpler. They just become more things to manage. Maybe I'm missing something and someone can point me in the right direction.

There are lots of pros on here who will find things like this trivial, but for someone like me (independent with limited professional dev training) the time investment is high as is the cost of "switching" between what seem to be mutually exclusive tasks (web dev/ops, and local analytics work).

This seems a bit...naive? Get a haircut and headshot as week 1 goals? therapist? look in the mirror? upgrade audio/video? what...? This is just a bunch of things to spend money on :/

Maybe spend the time finding a market with a problem that is lucrative enough to then spend time solving. And then figure out how to validate the problem...and then find a solution that you can get to market in a week or two (if not sooner).

This stuff isn't rocket science its just fucking hard work.

In my experience people can be both although they might prefer and/or excel at one.

A good "cowboy" is one that gets the job done but can also build a sustainable, changeable process in their wake.

A good "drone" is able to spot ineffective parts of the system/process and change it.

As an aside, I really dislike the cowboy and drone nomenclature.

I think it just boils down to that most of the time we are just plain wrong about what people want badly enough to change what they are doing already. Our other fallacy is that quality of work matters - like yes, kind of, but it matters far less than finding and fixing an "important" problem.

How many times have you encountered a piece of software that is utter garbage from a ui/ux/engg. perspective but gets used ALL THE TIME? plenty of b2b examples of this including back ends of banks. They are awful, but they work. The business solves a very real customer problem and the tech is just a supporting (although still critical) act. As long as the problem gets solved, the tech. does not really matter. There is obviously more nuance to this vis a vis software maintenance etc. but when starting up, the tech should matter to you less than finding a valid problem.

Well, zero criticism IS a form of criticism so I don't blame the author for not being motivated after the fact. I'd even say its the worst kind of criticism because it leaves you with nothing to build next.

But I think they are highlighting an important thing here that most of us struggle with...building is fun, progress is discrete and clear, the feedback loop is very tight. Selling and marketing to people sucks, its clunky, the feedback loops are variable, and if you're inclined more to being an introvert it is very exhausting.

I'm not sure the author is conditioned to fail as much as they are just more inclined to build.

Man, Langar is always awesome. They are not shy on serving size and the food is almost always legit amazing. Dont' miss out on the halwa!

One of the mind blowing things about this is the sheer amount of people some of the Gurdwaras end up feeding (1000s) and how non-trivial the whole process is from kitchen to serving. All volunteers generally.

Very familiar story. I'm 9months into quitting my consulting career after 10 years. Relatively long hours, weekend work, and lots of travel. The first few years were great, lots of learning, lots of smart people to work with, smart leadership, interesting and even innovative work.

But then it just got boring AND exhausting. The leadership became uninspired and replaced by the classic sleazy sales persona, the work became mundane, and the constant 4-6month cycle of new clients began to overlap as I went higher up and managed more projects/focused more on sales.

I haven't figured out what I'm gonna do next, frankly the networking burned me out so much I am very averse to it. And ironically I became quite good at it (at least relative to where I started).

I'm booking my first intro chat with someone next week, and already my stomach is turning thinking about scheduling it. I thought I was ready but maybe not...at the same time, life ain't free.

The best sales people I've worked with were incredible strategic thinkers and not really sales people at all.

They built an intimate knowledge of their customer and their industry, built strong connections with the top brass of their client by delivering exceptional work that got those people promoted, and were really good at building autonomous teams that could get the (exceptional) work done with their guidance on the customer/industry/client. These folks would also often deliver very difficult messages to their clients, which often resulted in more business not less.

The sleazy sales people can build decent pipelines/sales numbers but they are not what I would ever label as 'elite'.

[dead] 2 years ago

looks like...an automated blog? Suspect these are almost all completely fictional

Using a combination of both chatgpt and claude/sonnet. Codebase is not very complex or cutting edge (e.g., data pipeline to maintain a local db, and an analytics system). These are not enterprise or even public facing applications.

For additional context I have not been a software engineer professionally for over a decade but still am in the engineering field.

Usually I will feed in a few functions (or just 1), sometimes a whole module if it small enough, and prompt it for general performance, and maintainability improvements. I just kinda iterate from there. I also restart chats often

On one hand I agree with this conceptually, but on the other hand I've also been able to use AI to rapidly clean up and better structure a bunch of my existing code.

The blind copy-paste has generally been a bad idea though. Still need to read the code spit out, ask for explanations, do some iterating.

My biggest challenge with writing blogs/newsletters is the fear of publishing, not getting it "perfect", or being horribly wrong about whatever I'm writing about.

To get over this I just made simple personal blog/site using GH pages/jekyll/markup that doesn't have 1. A marketing version of a "publish" function and 2. the posts are perpetually in DRAFT.

Basically there is no 'done' which leaves me more comfortable in putting my thoughts on the internet instead of leaving them in my head. I can keep going back to the ideas and refining them.

I am working on making stats on financial securities accessible to more people so they can make better trading decisions. This is very much a work in progress.

https://www.statsviz.com/

A big part of this is me learning how to get code into production including infra setup etc. Any pointers would be greatly appreciated.

Stack is python, dash/flask, and gunicorn+nginx

A common scenario I've come across with multiple folks here (Canada, GTA) are couples where one does contract work and the other is a FTE. This gives consistent benefits with an increased overall income. There has traditionally been a substantial independent contracting market here but maybe that changes with the new macro situation we're in.

Yeah mostly cost related as others have suggested, I also use more cushioned shoes for training to help reduce fatigue for the back-to-back weeks of long runs.

I thought the same thing about gait but gave it a shot anyway. Didn't throw me off all that much, and I still enjoyed running in the firmer fly's. I did do a few trial short runs before the long run just so I was not going in cold.

To give an idea of shoe wear. I'll easily run through 1 pair in a year if I'm training for a marathon (just to run it). If I'm training to beat PRs then I'll go through almost 2.