Sometimes feels like its just generating really specific and personalised articles/blogPosts for me rather than handling any decisions or taking any load off me.
119 karma · joined January 29, 2019
Sometimes feels like its just generating really specific and personalised articles/blogPosts for me rather than handling any decisions or taking any load off me.
If you're selling a product, the promotional material has to be on point and amazing just to hook people in.
We're seeing lots of code being ~written~ generated, deployed, checked (tested manually), then shipping it as done. Fine for the simplist of things, but in a complex system unintended side effects are far more common.
I feel like the system analyst role is going to make a resurgence in the coming years. Once the domain knowledge is lost, there's going to be a need to re-discover it and understand what should be happening and what is happening.
Going against the grain - i don't think all but the most expensive (and non critical) SaaS products are going to be replaced by an in-house system. If you're company of 100 people is spending $12k a year on HR software. Building and running it yourself isn't going to save you 12k and in reality it's going to cost you headcount for someone to manage and maintain it. Mattermost exists and people still pay Slack $200 per year per user when they could just roll out Mattermost "for free".
I just assume all the posts that claim they've got a 20k line project in a single weekend is just marketing spam.
I did want it to improve our e2e testing but it didn’t make it as easy as I expected.
I mean sure, the next step will probably be "your ads have been seen by x real users and here are their names, emails, and mobile numbers" :(
As well as verification there must be teams at Reddit/LinkedIn/Whereever working ways to identify ai content so it can be de-ranked.
I have a relatively small workforce and office management platform. When MS Places was announced, we thought it was the end. We had a good run, but now one of the big players has entered the market and will wipe out all competition with a single swipe.
Anyway, it sucks. Potential customers who had waited for months tried to use it and immediately sought alternatives. Existing customers who told us they tried to use it and for one reason or another, gave up.
But it seems Microsoft's MO has been 'customer driven testing' for as long as i can remember.
I've tried it to generate html/css for an email and it kind of works but depsite asking it to doesn't work across all versions of outlook and gmail.
I'm overly cautious about what I paste in. Just like how you can find PII data in logs I think the amount of PII data that's being pasted into AIs will be crazy.
Anecdotally, and from the companies I know that do have a graduate program, they've reduced the number of available positions, so there are still positions, but it's just much more competitive.
My advice would be to find any role roughly related to your target job and then pivot to what you really want. The difference in interviewing a candidate with no experience vs 12 months is night and day.
10 years after that will be interesting. Can you imagine a $100m business running on dozens of apps generated by various LLMs. Are management going to sign off a rebuild from an LLM or are they going to get a team in to do it from scratch and consolidate the systems.
Agile principles will be back, "Individuals and interactions over processes and tools" will be a popular line.
I very much doubt we're going to see a massive shift where everyone becomes a system analyst or service designer and we just punch in business requirements out comes a ready-to-release system.
I can see automated ui testing tools becoming truly amazing if AI Agents are even half of what they're hyped up to be. At the moment they kind of work, but also a bit of a headache.
For some time Twitter seems to have been the defacto real time announcement tool for companies. Now Twitter has been made private seems ripe to be replaced by a startup.
Positioning yourself correctly, too low and you'll never get past the sea of grads.
Distill your history down so it appears you've had a more stable career history. A random HR bod is going to review your CV and they do not care how many startups you've founded or accelerators you got accepted into. If you've got loads of entries in your career history they're going to stick you on the no pile.
Regardless of how it is internally, corporations don't like lone wolves or individual contributors. They have 'company values' and want someone who works well in a team, has done some mentoring, works well with others, understands the processes, etc etc etc (that is until you start then it's all about delivery). I'd try positioning your CV to appeal to those values with the technical skills to back it up.
In summary - lose the fluff from cv/applications - present a more stable career history - emphasis on teamwork, working with other departments, mentoring
And, I wouldn't worry about AI, offshoring - yes, AI - no. I'm still waiting to be shown an AI-generated SaaS app with real users, or even a functioning tool that's not just a clone of Flappy Bird.
I, and im sure many others, can do without the stream of BS that comes out of LinkedIn. But as far as an online job history and to search for companies, it's quite useful.
Agency life is probably 80% sales and 20% delivery. The agency pattern you've mentioned is common because it consistently works and everyone (myself included) fawns over the basecamp model but they're about the only ones who've made it work.
AI-generated SaaS tools just remind me of white-label SaaS products that were the hot thing however many years ago. They do about 50% of what the customer wants and a PITA to customize.
Having said that if I started again I'd still build one or more AI-centric B2B products with a focus on closed AI systems and look for agency work (ad-hoc development) as an offshoot.
You'd be able to build up a client base with your B2B products and have tangible examples to demonstrate what you're capable of while playing on the fact that the client's data is secure and never shared with third parties.
In the backend, limit image size to say 50mb, the number of images a user can upload to 1k and the amount of users that can be signed up to 10k. Then you have some numbers which will let you say "regardless of what happens, I've got a hard cap of 1 TB of stored data".
You don't have to show the user their usage and you can always lift the caps with a deployment. What you don't want to happen is a side-project costs you tens of thousands because one fool thought it was funny to upload a million hi-res pictures of Rick Astley while you were asleep.
Slightly more work would be to limit the number of images that a user can upload in 15 minutes. Or depending on what your signup flow is making a user confirm their email but putting a short delay in sending the email out.
I must admit I also ask this question but have never been told not to and I find that every so often you come across a very senior candidate who nonchalantly says 'yeah, I built a plugin for abc that helps me xyz'. Then you look it up and they've got 500k installs.
I don't have any overseas adventures though (:
Remember - you're only 30, you've still got time.
Small ideas will need less maintenance and constant development but you could spend more time on bespoke features for customers.
Small ideas win everytime for me.
Nontech roles are just a sea of prompt-generated answers, they don't tie into the applicants' experience and are usually about 200 words of waffle. If you're applying for something, type out a few sentences then give it to a prompt to refine. Don't just paste the question in.
Tech roles we focus on the combination of soft skills and technical skills and so we've gone back to a 'pair' programming exercise and a whiteboard architecture exercise. In reality, it's just a spectator sport that we nudge them forward if needed.
In Java looking for them to cover the basics of debugging a problem, writing a test, and mocking out some services. I would say 50% are unable to or unwilling to write a test to prove the error or don't know how to mock out a service.
Whiteboard exercise looking for them to explain a system they've worked on in the past. We question some of their decisions and see how they handle themselves. Not many get defensive (though some do).
You can do it whatever way you want but match the style of the project. I've worked on too many projects where someone decides their way is best and you end up with a mix of everything.
If you want to change the code style, okay, but change it everywhere and don't forget to test everything you've changed.
> Frontend development is a nightmare
But is it weird I kind of enjoy it every so often/
> Elegance is not a real metric
You're dam right it's not! Next time someone proudly presents a super elegant, refined, and minimalistic solution I'm going to phone them at 3am on a Saturday and get them to debug it while screaming at them about lost revenue or something.
> DynamoDB is the worst possible choice for general application development
Oh man, the amount of times I've seen some form of noSql and it's used as a relational database. 9/10 some rendition of SQL is more than sufficient.
In two cases legal said hell no after the prototype. One was mine and the state of hardware and the ux wasn’t good enough to release.
Legal said no to: Listen to songs for free by taking meta data of freely available radio station recordings (like what’s available for 7 days after broadcast) and just playing the x many minutes of the show that the songs on.
Taking sports f25 sports data and generating a live top down 2d view of the event. Legal said no.
Playing html5 games on a tv using your phone as a controller via a chromecast. You could probably do this now with a QR code and web sockets or something.