At thirty I quite my job as an industrial painter and sandblaster and started as a temp data entry clerk at a local government for $8/hour. Worked hard at what I did, made connections, and moved into field-work, then GIS. From there I moved to the private sector in Civil Engineering, still doing GIS. I then made a tangential career change into geospatial software development after moving to DC, as I spent a lot of time learning programming on the job as a GIS Analyst. Now I do DevOps. I think the key for me was to put myself into an environment where I could get the opportunities that I wanted, and working hard towards those goals.
This is great. It's interesting how two very remote dwarf planets with widely different orbits are so close to each other right now (90377 Sedna and 2012 VP133).
EDIT: On further thought, I noticed another kind sorta nearby. I wonder if this is just a matter of looking for them in that area and that there could be a lot more that are undiscovered?
Your edit is spot on — there's a lot out there in the Kuiper Belt / Oort Cloud that we don't know about. It's hypothesized that there are many objects out there, with more mass than in the Asteroid Belt. It's no coincidence that the ones we know are all near their perihelion currently.
It's geared more towards collaboration and there is some system to share any income that gets derived (not sure how it worked). You find someone's song page, download the existing tracks (stems) and work on your own, uploading to the collection when you are finished. I collaborated with some artists and it was fun and I met some folks. They set up payments but I never expected anything to come from that. I thought finding projects that are interesting to collaborate on was difficult. It's just a big pile of music of varying quality and genres.
Depends on your definition. I created a mapping application that allows one to navigate and style the map with natural language (more or less) as well as some prototype database interaction. When the user inputs a prompt, it gets sent to an "agent" whose sole purpose is to send a request to the API with a custom system prompt with few-shot examples stating something along the lines of "determine which agent should handle this request...only respond with one of [NavigationAgent, StyleAgent, ...]". When the response comes back, the prompt is then sent to the proper agent to handle the request. Each agent has function definitions for properly returning parameters to use to manipulate the map. I don't use any special libraries like langchain or anything, it's just regular API calls organized into classes that have specific system prompt behavior defined, function definitions, and some user prompt context ingestion when required (e.g. the current extent of the map).
I call them agents just because. I'm just doing function calling with custom system prompts for the most part. It's hardly complex, I wrote most of it in a few days.
EDIT: I should add that the first step is used to cut down on the number of function definitions I need to send to the model on each user prompt. Navigating a map can be done with as few as four function definitions but styling a map gets out of control fast (google "Mapbox Style Specification" if you want to see why).
I use Apple TV through the website (laptop driving the TV). They are the worst with bugs and UI design choices, at least on Chrome. Will the space bar pause the movie when I press it? Maybe!
reply