IpV8

I am currently building something similar for my company. We are enabling people to host apps with python backends as well, so that people can do more complex tweaking of data for scientific workflows. The out-of-box solutions keep users constrained to an environment that doesn't allow things like importing weird packages on the back and front end for custom apps. The security implications are challenging, but I can mostly just keep the apps hosted in a highly constrained environment.

Separately I haven't yet seen a great security governance model for LLM integrations. At an enterprise level I'd like to govern rules such that, for example, if someone gives an LLM access PII information or proprietary data, then it shouldn't have access to a slack integration or the internet. Controlling this at the employee or team level doesn't make sense, as an employee may have reason to make separate use of both. From a security perspective I want them to be able use LLMs with different types of acccess, but not necessarily the same agent at the same time. Furthermore, they could ideally chain together agents with different permissions in specific orders. For example they could have a workflow where an agent can reach out to the internet, and then have a separate one that can read/write to slack, and then have a third that can interact with PII data. If they tried to wire together agents in the opposite order, it should get denied.

I have tried this a few times. If you live in the woods with lots of standing water, then it has literally no effect. I bought a giant supply of bacillus thurengensis pellets and put them in every body of standing water around the property weekly for a whole summer and still got annihilated by mosquitos. Now I spray, and while I hate pouring chemicals all over the property, it works fantastically well.

I could imagine it working alright if you live in the city or maybe a suburban area.

Absolutely, every time I have had a job that I couldn't answer these two questions with a confident affirmation, I have burned out in under a year. It certainly is a trial of your moral hierarchy when you are forced to pit financial and opportunity against your core values. I understand why people choose otherwise, but for me it's barely a choice.

Fuck all the people responding to with shameful posts about breast feeding being better. I did a fair amount of research into why, and the only conclusive thing a found was that breast feeding increased IQ by like 2 points. That is massively insignificant. IF breastfeeding adds antibodies (which is debated), then that is more than offset by just being careful to not let your child be exposed to the flu. The happiness of your child long term is by far the most important thing, and if being able to sleep better allows you to be more attentive to your child's emotional needs, then that will drastically out way 2 points of IQ. Most people telling you breast milk is better probably have no idea what it is like to feed a baby 8+ times a night and the emotional and physical toll associated with that. That type of situation can make you resent your baby. These people probably read about breast is best on some inlfuencer's blog or are parroting back some advice that their doctor gave them based on their particular situation. A mother who can't breastfeed for physical (or even emotional) reasons doesn't need an arsenal of people explaining to her why she's damaging her baby everywhere she looks to add on to the shame and inadequacy that she already feels. /rant

Location: Portland, Maine Remote: Yes Willing to relocate: No Technologies: Python, SQL, AWS, ETL, Any relational database (mysql, postgres, sql server, snowflake, etc), elasticsearch, Linux/Unix and many more Résumé/CV: Available on request Email: [email protected]

I am a solutions architect/senior software engineer with experience solving complex problems and scaling cloud services. Recently I have been more focused on modern data warehousing techniques and ETL. I enjoy designing data intensive applications and then working on the ground to break down the architecture into smaller pieces and setting up a development environment where juniors can succeed. I have experience managing/mentoring junior engineers in this context.

Do a search, there was a thread on this yesterday and another a couple days before that. The summary is read a book or two but be ready to adapt to your babies individual needs. Prepare to lose any semblance of hobbies or personal time, and say goodbye to a good nights sleep. Oh also your significant other and yourself will almost definitely experience a significant mental health decline within the first 6 months, so I hope you guys already have figured out how to support each other because thinking rationally and building new relationship habits with only 5 hours of sleep a night is a struggle.

Edit: It is also super cool to watch a new person discover the world. Enjoy your time with them!

Come to Maine. Billboards are illegal here! All of the surrounding states talk about how beautiful it is here, I think that a huge part of the beauty is the lack of forced exposure to advertisement on our highways. (though the beautiful and well preserved landscape and coastline doesn't hurt either)

I'd say higher demand led to more R&D. Supply alone wouldn't drive the price declines, as it used to cost too much to produce high battery capacity so there was a price floor. As demand increased, justifying the R&D helped break down that floor. That and government dollars.

I have only really done technical interviews. My process is to give the resume a once over to understand what technologies and project they have used that I have a deep understanding of. I then prepare a few questions around those areas and order them in increasing difficulty. First I'll ask someone to describe the project, then I'll hit em with a question that proves that they actually did what they claim, then I'll ask them a question meant to push their limits and see how they react. Finally I get to my most important part, which is taking whatever project they described to me and then asking what they would do if their boss came in today and tweaked the requirements. I'll use a requirement change that would force a serious re-architecturing. Exe you built a crud app, what if you needed to support 10,000 concurrent users? You made a data extraction tool, what if it had to extract 1000 Gb of data instead? You built CI for your project, what if that project had 30 developers? These types of questions tend to show how a developer thinks. The hard part is making sure they are comfortable enough to brainstorm with you, as many technical folks would tend to close up under a lot of pressure. Basing it off of a project that they already know well tends to help give them a starting off point.

In addition to this, I like to give them a real problem that the interviewing team has experienced recently that is within their claimed knowledge base. For example if someone claims to be an aws microservice guy, I'll ask them about a time when our AWS ECS jobs needed to decrypt files that were bigger than the maximum allowed disk size. There are many different ways to get around that limit, but they all have tradeoffs.

Fist off, its a virus not a microorganism. Second, high humidity reduces the spread of viruses. That is why you get the common cold more often in winter, when it is very dry.

We're starting to see the mass layoffs begin. I wonder how much effort it would be for a company like Amazon to employ them as Temps. There is going to be a massive increase in availability of skilled workers looking for something to fill the gap.

I forgot to answer your other question about tracking employee engagement. We make people track their work down to the 15 minute increment, and make sure they hit specific allocations per project exactly. We also micromanage their tasks in Jira so all of the time tracking lines up to tickets.

For the love of god do not do this. Engineers hate this and flee from it in droves.

We like to encourage developers to go for certifications in the technologies that we use (AWS certifications, Snowflake certifications, etc). Our vizualization folks get Tableau and PowerBI certified. We also have some Tableau admin certified people. This way you have a measurable qualifier that someone is training in a relevant skillset. We allow developers to spend a certain number of hours per year on training, and reward them with raises (500 or 1000 dollars per year) when they achieve their certification. We are flexible about what certs people go after (as long as they are relevant to the business). We also try to send people to conferences hosted by the relevant company once they pass the exam (re-invent for example).

Hah, too true.

I find giving them smaller, well defined tasks and checking in frequently helps erk some productivity out of them. Also having lots of check-ins and pair-debugging sessions opens the door for a lot of mentoring opportunities. If their still bad, send 'em to tech support or QA! (only kind-of kidding)

I think you're on to something here. I certainly value a lot of freedom and need the challenge of solving big problems myself. I get demoralized when some scrum master is breaking everything down into tiny tickets and only doling me pre-thought out bits of implementation work.

Lets assume for a second that you're right and focusing on sprint targets is bad. How else can we solve the issues that Scrum solves well? Management knowing what their team is working on, Management being able to prioritize features, Not losing developers to time sinks only to surface weeks later without any significant value add. etc. etc.

I've found some success with setting 2-week goals as large items. Give a good engineer clear requirements for an entire business goal that will take roughly 2 weeks to solve, and then give them huge liberties of how to implement. Though do the same for bad engineers and you'll get comically disastrous results...