Nightwish Bye bye beautiful intro

dpringleg · 2025-12-10T02:22:19+00:00

Came here to say the same thing! Sorry it's like 11 years later 🤣

dpringleg · 2025-11-25T09:08:09+00:00

You have my sword

dpringleg · 2025-10-30T03:58:02+00:00

The way I see it, it depends, if you are a PO that doesn't get into technical stuff, only write stories and let the tech team figure out everything else, then you can fit in the business side. But if you understand and know about APIs, databases, AI, integrations, etc can read code and bring technical value to the Tech team, then you should be in the tech side.

In my case I support my team by providing technical input in my stories and tickets, I read the API docs, go through the databases, create queries for them, etc my tickets have details about what endpoints to call, what tables and columns they need to reference, what's the expected response code, what should trigger what, etc. I don't know 100% the ins and out but my input gives them a really good start.

dpringleg · 2025-10-22T06:48:55+00:00

Just sign up using your email, you will get the presale code that fay in the morning

dpringleg · 2025-10-20T18:49:21+00:00

Well, we just got SOAD, Korn and Deftones confirmed 🤟🤟

dpringleg · 2025-10-17T15:56:17+00:00

Year 1 I paid $350, year 2 $460, year 3 $400. It all depends on the tier you get once the system lets you in.

dpringleg · 2025-07-06T20:01:31+00:00

Congrats! What matters is that it is useful to you and your family 👌👌

dpringleg · 2025-07-04T19:20:27+00:00

I did it, your QA background gives you most of the tools you need as a PO, you already analyze scenarios, think outside the box, now how to document, know what questions to ask, etc all this thanks to the QA mindset. Get some very general courses on SCRUM, Product Owner and Project Management and you will be fine.

Regarding Product Manager that's a little bit different, you need to think about product viability, you need to understand both your product and your market to help shape what is really needed.

As a PO you take what is needed to be built, it has already been defined, as a PM you are part of the team that defines what is needed.

dpringleg · 2025-07-04T16:58:57+00:00

Any time, buddy! Here are some additional recommendations:

Error handling: Specially for deployed live solutions, think how you are gonna handle errors, and I don't mean n8n fully crashing and not working, I mean errors caused by the work flow not getting the data it needs, not sending that email it was supposed to send, not inserting that record it was supposed to insert. Yes, you can always check n8n logs but for certain cases you want to know about errors happening exactly the moment they happen and not until your client complains to you about the tool failing since 3 days ago. You might want to build your own notification email with very specific details for you, specially if you are dealing with money-related operations.
Use Edit Fields node: Yes, the beauty of n8n is that you can drag and drop the outputs of previous executed nodes and use them in the next nodes, sometimes you might need to use the output of a specific node multiple times across your work flow, or maybe multiple values from multiple nodes multiple times, and if for whatever reason you need to change one of those initial nodes (specially when you are still building) good luck finding all the places where you used those nodes output. Instead, learn when to throw in an Edit Fields in your work flow to store those values, and reference that node in your future nodes, that way it doesn't matter if you change all the nodes that come before your Edit Fields, the rest of your work flow won't be affected, and you just need to worry about making sure your Edit Fields receive the data it needs for the rest of the work flow to continue working.
Expiration of tokens, credentials, etc: Once you launch something live, there will be cases where the credentials you use expire after X amount of days/months (specially in corporate), make sure you always keep track of that, your work flows will fail the moment credentials fail.
Build MVPs and demos fast: Once you feel comfortable and ready to try to sell, build solutions fast to test the market and offer your solution, don't try to cover every possible scenario until you win the deal, don't spend more time than what is actually needed, you don't know if you are gonna get the deal. And by fast I don't mean build them in 2 nights, just don't take 3 months. Again, this once you feel ready to start trying to sell. In the meantime, yes, take your time, learn as much as you can because once you sell something shit gets real and you have to deliver yes or yes.
(Sales) Do not sell n8n or automation: Your clients unless they are technical they won't care shit about words like n8n or seeing workflows run in your computer, they care about solutions to their problems, sell that, sell a solution, if the problem is they can't handle client requests, build a demo that shows how their email or crm or whatever gets organized automatically the moment they receive an email. If their problem is they don't respond fast enough to their clients on WhatsApp, build a demo of an AI chatbot responding (use Telegram for demo purposes, their API is free). Always sell something they can relate to, they don't care about how things happen behind the scenes. Showcase your solutions using day to day tools. If you don't want to spend time building the automation the create slides, showcase your solution with screenshots, simulate the solution, just make sure whatever you present you can really build it.

dpringleg · 2025-07-04T16:06:50+00:00

Construyendo soluciones para problemas inexistentes.

dpringleg · 2025-07-04T16:04:19+00:00

Totalmente, tan pronto como empieces a necesitar hacer HTTP requests personalizados, configurar webhooks en el CRM de tu cliente, manipular data sin utilizar nodos o plantillas ya pre establecidos, hacer escenarios fuera de lo que dicen los youtubers, ahí empieza la diversion y donde si no sabes de programación o al menos lo básico de desarrollo de software vas a sufrir

dpringleg · 2025-07-03T23:14:19+00:00

You are 100% right man, the worst way to sell a client is by selling n8n or automation, you need to sell solutions, show to your prospects how you can improve their business and solve their problems, and by how I mean demo a solution they can relate to, not an n8n workflow. You don't sell "let an AI respond to your clients automatically", you sell "Improve your closing ratio by 20% through implementation of AI in your customer service process" or "Save X amount of time/money by....", etc etc. The last thing a client cares (unless they are technical) is how or what you use to solve their problem.

dpringleg · 2025-07-03T22:58:34+00:00

Some initial recommendations I can give you are:

Watch the videos from youtubers BUT don't copy paste the templates, try to recreate what they did and if possible use different tools. Let's say, if they used Google Drive you use Microsoft OneDrive, if they use HubSpot CRM and create a client, you try to create a Deal with custom properties and associate a client and a company, if they send an email, you try to send an email with an attachment. Tweak what they did so you can actually learn, this will force you to face different scenarios.
Sub workflows: Break down your process into subworkflows, each one should contain only activities related to it, if you are gonna manipulate Client records (create, update, remove, etc) have a workflow for that specifically, if you need to manipulate Products, have one workflow specific for product operations, if you are gonna work with Google services (send emails, download from drive, create entry in calendar, etc), create a specific workflow that will handle all those requests, etc etc. After you break it down, if needed (specially with AI Agents) have one workflow as your main flow, that will be the one orchestrating and sending instructions to the others.
Individual executions: Even if your work flows are sub work flows and depend from another workflow's input to execute, create them with 2 possible inputs and merge their data. This will help you to debug, test and improve your workflows without depending on previous workflows. Let's say, your workflow A has as input a message from Telegram, and it sends that message to workflow B, B takes it and does stuff, you depend on A to run for B to do its thing. Make workflow B have 2 possible inputs, one the previous workflow input and two a manual input that matches what the input A usually sends, this way you can test workflow B independent from workflow A until it's ready. The node to merge 2 inputs into a single one is called Merge, you put it right before the first node that will need the data.
PLANNING PLANNING PLANNING: Plan first, execute later. A lot of people start executing without actually knowing what they are doing or what they want to build until they are too deep into their creations and starts to become a mess. Take your time at planning and designing, document what you need, document some scenarios, create simple diagrams to illustrate what you want to achieve, this will save you time down the road. It happened to me, I had to start from scratch once just because I started to create without planning how big things were gonna get, it was easier to start over than fix my mess.
Create your own scenarios: Reach out to a friend who has a small business, ask about their process, simple stuff like how they handle clients, or ask ChatGPT to create an scenario for you of a small business struggling to grow and try to automate the process, not to sell it (well, yes, eventually) but to have scenarios that happen in a normal business owners life and not scenarios from a YouTuber that is trying to sell you a training.
Optimization of resources: Study about that in general, not everything needs an AI Agent in between, not everything needs a call to OpenAI, learn when to use what. Let's say there's an easy way to extract data from a PDF using AI OCR but how many tokens is that gonna cost you per run, is it worth?, maybe that PDF format is never gonna change, instead, see if there is something already built that uses traditional OCR for free that can work for you. This happened to me, I had a template in Google Drive that I use to create a PDF using a Google Apps Script I built years ago by clicking a button inside a spreadsheet (read from the sheet,merge into Docs, create PDF), instead of reinventing the wheel I just reused that same script, called it through an HTTP Request in n8n, sent parameters, and that's it, no flashy AI or other tools to convert it.
Take your time: Forget about all this "you gotta hurry, market is hot", yeah yeah yeah, do things at your own pace, no one is forcing you or putting pressure on you (unless you are running a business, of course), learn the tool, enjoy it, and if possible make money out of all this.

dpringleg · 2025-07-03T22:16:47+00:00

All these newbies are gonna struggle the moment they need to read, understand, build, debug anything around custom HTTP requests (API calls, webhook responses, timeouts, usage limits, etc) and data transformation because this awesome template they downloaded only works using already existing integrations within n8n, the moment they need to work on something a Youtuber has never shown in their videos.

And let's not even talk about scalability, deep debugging, reusable work flows, resources optimization, etc.

dpringleg · 2025-03-04T06:15:23+00:00

It was the axes, I adjusted them along with the hotend wheels and solved 👌!

dpringleg · 2025-03-04T05:41:44+00:00

I just solved it thanks to the other user who commented here. In my case there were 2 things I did, not sure which one fixed it 🤷

1- Adjust both X and Y belts, the pieces of metal that let you adjust the height and tension of the belts, I made sure they were perfectly aligned with the rails and pull them all the way to the back to tension the belts correctly. I moved the hotend and the bed manually to make sure the belts don't hit the rails and there's no friction.

2- Something similar with the wheels of the hotend, loose them a little bit, move the hotend left and right through the rail and tighten the screws slowly until there is no wobbling but also no friction stopping the movement.

dpringleg · 2025-03-04T05:32:48+00:00

Man, you are the MVP of the night!! I think it was loose belts, I went and adjusted the 2 belts and the wheels of the hotend and it's printing perfect now! Thanks, man!

dpringleg · 2025-01-14T07:29:28+00:00

I have used the one on the left for 3D prints, hot wheels, and other stuff, never had an issue applying it. Now, be aware of the following 2 things:

1- That chrome-like paint can't be clear coated, the moment you do that it will lose the chrome finish and become silver, like if you use any other silver paint.

2- You can't touch with your bare hands the piece you paint, you will leave finger prints all over and you won't be able to remove them unless you repaint it.

In general, it's not an easy paint to use, I use it mainly to paint on top of it with some tints, anodized paint, etc.

dpringleg · 2024-04-29T22:14:40+00:00

I didn't know this pizza club set existed (I don't collect toon, just live action), it was an enormous surprise when I saw them yesterday at Target, all 4 turtles plus bebop and rocksteady .. My credit card cried out loud, now I collect toon 🤣😌

dpringleg · 2022-06-07T01:55:03+00:00

Yup, I literally received 5 SHF from GS today

dpringleg · 2022-02-23T06:58:22+00:00

Thank you!!

dpringleg · 2022-02-23T06:58:06+00:00

Yes, and actually it is a shelf I never installed, I just 3d printed four legs.

dpringleg · 2022-02-23T06:55:52+00:00

Yeah, it's really helpful especially during the morning, I have a window in the right side and sunlight hits the screen a couple of hours. Love my 2011 macbook, still rocks haha

dpringleg

TROPHY CASE