Cool project regardless!

Humans now can choose to either completely surrender to that external intelligence, called cognitive surrender or choose to just offload tasks and use it alongside their own reasoning.

It's up to us how to use it. I've recently joined a new company and I had to explore their massive codebase. Even my manager suggested that I should use an agent to help me with the onboarding but I went straight to the code and whenever I had a new task, I would explore the code to understand what is happening and then instruct the agent to do any tasks I thought should be done.

There are moments when I completely hand off to the agent without looking any diffs, but my main focus is understanding first and then handing off.

1: https://www.researchgate.net/publication/399711077_Thinking-...

I'm building a chat-assistant that will be able to discuss with you and find more about what's your current work status and what you're looking for. Then it will suggest best suited roles for you from the HN Who's Hiring threads.

It's still very early, I've managed to index the latest thread and there's a CLI chat tool to discuss with the LLM.

It's been great because I learned a ton already, about LLM deployments, RAG evaluation, prompt engineering, LLM internals, etc.

https://github.com/kbariotis/hn-jobs

I'm looking into docker-compose with remote docker-compose yaml files but I'm not sure of how solid is going to be.

Our services are mostly Node.js based services and dockerised already. Production environment is setup on AWS ECS.

Comments URL: https://news.ycombinator.com/item?id=37319487

Points: 5

# Comments: 3

Regardless, GDP is always useful so def one of the right metrics for economic performance in general.

Def I need more studying on the subject my self.

I would like to evaluate my country's (Greece) last government performance and what real effect it had over the country's wealth and the general population.

That is only for personal knowledge purposes and not for a professional/academic inquiry or something.

Thank you

Comments URL: https://news.ycombinator.com/item?id=36584945

Points: 1

# Comments: 5

https://www.amazon.com/-/es/Brian-Christian/dp/1627790365

In all my experience, the agile product development process has been pretty much the same. For example, in my latest role, the PM will verbally or in a very short and vague document describe something that we want to build to the Engineering Manager (or to one of the engineers) and then they will gather the engineers to refine the problem by discussing possible solutions and as an outcome we will produce tickets that are ready to be picked up.

While this process has been working fine, we always had the same complaints, a) very vague requirements b) no documentation/history produced during the process and as a result, in a few months we will have forgotten what we've done and why c) communication between engineers and stakeholders is rare and as a result, many times, the stakeholders will receive something else that what they actually needed d) very poorly written tickets description exactly because the communication is poor.

I've been trying to figure out what could be a better approach but because my experience has been the same, I'm not able to sell any alternative to the team/stakeholders. I've reading about user stories and other agile-related solutions but I'm struggling to understand the nitty gritty details of such a process.

What is your current process and if possible, describe it in as much detail as you think someone that has never done it before will understand.

Thank you

Comments URL: https://news.ycombinator.com/item?id=35466575

Points: 1

# Comments: 0

I’m only trying to make sure I understand the problem otherwise I cannot evaluate the solution. Plus it would have make it very hard to sell it to me, if I was to take the decision.

Data are everywhere these days and you should be gathering as much as you can(emphasis in can, it can be expensive). Take Google Analytics for example added to a blog, you can see your most read articles and write more of those, see where people exit and take action, setup interaction tracking and see what buttons are working best. You can do AB tests and compare results between two comment forms.

Same logic applies to a product as well.

But then it’s not just analytics and valuable information can be extracted from everywhere. Look at your DB and see what people have been storin (being cautious on prívacy laws). Gather NPS and see what feedback you’re getting from there.

Big companies usually have departments focused on data gathering and analysis, but even for smaller products, I would say that the best thing you can do is being data driven. Try to base your decisions with data that make sense.

All the best

I bought a Mignon Zero grinder and a Delonghi Dedica with a non-presurrised portafilter for about $500 for both. Both are beginners friendly and for home use. I've learned all about dialling an espresso, the amount of coffee to put it, the duration of the extraction, the amount of coffee to get out and what role the cut of the coffee plays.

I've calculated that the investment will pay back it-self in a few months, ~5-6.

But seeing that your experience is mostly on FAANGs and big companies, have you thought of going with a smaller early-stage company? These are environments where people usually expose them selves to a broader spectrum of things, even having the ability to choose specifically what they want to work on.

Workplace politics unfortunately are everywhere, small or big companies. You can't really avoid those.

I also can't stress enough other replies here about really exploring your self outside of work. What do you like spending your time on outside of working hours? Any hobbies that take your mind off? If there aren't any, can you start exploring new activities (without necessary having to take a sabbatical or move to another place?)

Nowadays and after lots of years of experience mainly in early-stage startup environments, I don't even care about the code or the low level stuff.

I'm trying to embody my self to the mission. I'm looking for the right metrics to watch and when these metrics are impacted by my actions (or my teams' actions because these environments tend to be very team-driven) thats when I get the same feeling as when I was writing those Visual Studio LoCs and was building those grey UIs with MS Access for data storage.

With the right mission and metrics, comes a problem. With the right problem that will motivate you and excite you, comes the solution. And the solution will be a package of the right code, the right UI, the right line of communication, the right team policies.

I've stopped using the term software engineer for my self, I prefer the term product engineer. And building the right product is my mission.

If you haven't explored that path, of changing your perspective of what gives you that feeling, maybe it would be helpful before deciding to go live in a farm. :) All the best.

I would also like to hear from people that went through that path and where that lead them because I'm still early in my career (in my 30s now).

> Kostas Bariotis is a software engineer who works at Grover, as well as being a co-organizer of a few tech events. He also has a podcast called Devastation. On his website, Kostas writes articles about topics related to web development like TypeScript, GraphQL, Docker, and npm. He also talks about his experiences in life and shares his passion for writing clean and efficient code. He encourages people to read more about him and get in touch. His website is open source and it was designed by Thanos Theodoridis.

I guess that they are not obliged to deal with it at least in most countries. I honestly don't know much on this space but this article raised my curiosity.