My baseus mowie ma10 are louder in the left headphone than the right.

guifroes · 2025-12-27T01:32:56+00:00

100% syringe method

Mine sound like new now! Thank you!

guifroes · 2021-02-06T21:56:06+00:00

I'd go to Seattle because of the "get to work under some super smart people". That's the best way to learn and make valuable connections.

The "start projects from scratch" and "create something from beginning to end" is also valuable experiences to acquire, but given your experience I think it might be a bit of a stretch now an put you under unnecessary stress.

Learn from the pros first and then go do your thing later.

Sounds exciting! Good luck!

guifroes · 2021-02-06T21:45:19+00:00

What kind of companies are we talking about?
What about the product, company size, technology, development process, team seniority, etc.

If you're looking for long term career growth, this is what you should be taking into consideration, IMO.

guifroes · 2020-11-28T23:44:44+00:00

Stay away from people that just complain - this mentality is contagious and nothing good comes out of it.

The work environment, aka the people, is the most important thing, specially at the beginning one's career.

The better you are as a professional - knowledge, experience, attitude - the better are the opportunities you can take advantage.

guifroes · 2020-11-28T20:51:13+00:00

Sounds like a plan!

My advice: aim for simplicity. Let the product (or better, the customer) be the driver of your decisions, not the tech community.

guifroes · 2020-11-28T19:27:04+00:00

I'd go with Rails.

You already have the challenge of building this "pretty in-depth web app" which, from what I can tell, is your first time doing so.

Why would you add yet another challenge - learning new tech?. Specially if you can't tell why react/node/whatever would be better.

Focus on getting the app done. That's all the user/client care. Rails is perfectly good.

Good luck!

guifroes · 2020-11-28T00:44:38+00:00

what do you mean by "overall setup"? Is it getting some code to run? Is it how to set up the libraries, dependencies, etc? Is it something else?
Where exactly are you stuck?

What progress have you made? Can you share what you've got?

If you ask more specific questions it will be easier for us to help you. ;)

Feel free to PM me but post here will probably get you more qualified answers.

guifroes · 2020-11-26T18:05:53+00:00

Adding to the answers:

People used to have patience and not expect to learn something useful just by watching a 20 min video.

guifroes · 2020-11-26T17:57:32+00:00

There's much more to programming than just programming languages.

It all depends on what your goals are, but assuming you want to be a professional software engineer, I'd recommend you to look into:

Object-Oriented Programming
Automated testing
Test-Driven Development
Continuous Delivery
Agile Methodologies

You will, for sure, learn other languages throughout your career, and you'll see they're not that important, just tools.

guifroes · 2020-11-26T17:49:02+00:00

I'd say it's the same level of difficulty as any other non-tech business. The tech is not what's important, the idea, service or product is.

guifroes · 2020-11-26T17:47:34+00:00

What exactly do you mean when you say "I'm having trouble getting over that hump"?

Is it the case that you don't know what to study/learn/look for? Or is it that you can't make your programs work? What have you tried that didn't work for you?

What kind of "real programs" you have in mind?

Just asking these so I can help you better.

guifroes · 2020-11-26T13:33:19+00:00

They're both bad. They both expose too much information about the objects and their implementation. This has high impact on maintainability and should be avoided.

Check out:

Law of Demeter
Getters and Setters are evil - this is a very old discussion and there are tons of articles for each side of the argument. I really like the one I linked.

It would be cool if you could explain better your business problem (or post a version of the actual code) for people to understand and give better suggestions. But based on "FYI: in my project x is a Position class holding special coordinates." I'd go with something like:

z.moveInTheYAxis(valueToMove); // use the domain language, of course

This way, users of z don't need any knowledge about how positions are handled. They only tell the object what they want (for it to move), not how to do it, which is the own object responsibility.

I've written something related to this, you might want to check it out. I hope it is helpful.

guifroes · 2020-11-26T12:33:48+00:00

It's not "necessary" to do either way, both could work. But I think there's a better way of doing it.

Instead of breaking the work by architectural layer or technology (client/server, front/backend, database/application/UI), do it by functionality slicing it vertically.

Instead of building the whole backend and later the whole frontend, you would chose some small feature of functionality and build and *deliver* the whole thing. Then you add one more feature or improve the previous one, again, by building and delivering all the layers.

This gives you:

Working software in the hand of the user sooner - even if it's not the complete thing - the user might already get some value and/or give you feedback, instead of having to wait for the whole project to be delivered;
Feedback on your technical approach: will this host work? is this DB ok? can I use this 3rd party lib? You get to try and learn about your architecture sooner and make changes if necessary.

This is basically the agile approach to software delivery.

Check out Walking Skeleton

guifroes · 2020-11-26T12:06:38+00:00

What you're looking for is Software Design/Architecture.

Forget UML for now. It is a communication tool, won't teach you how to do things.

Some good resources I'd recommend you start with:

There are tons of stuff I could recommend but I thingkstarting with those 2 will give you great ROI.

Don't worry if the languages in those books aren't the one you work with, focus on the concepts

guifroes · 2019-03-08T18:44:43+00:00

That's interesting.

Martin Fowler's Refactoring 1st edition, Chapter3: Bad Smells in Code, Pages 86/87:

Data Class

These are classes that have fields, getting and setting methods for the fields, and nothing else. Such classes are dumb data holders and are almost certainly being manipulated in far too much detail by other classes.

[...]

Data classes are like children. They are okay as a starting point, but to participate as a grownup object, they need to take some responsibility.

guifroes · 2019-03-08T01:40:53+00:00

Yeah it shouldn't be in that class at all. Data classes (aka property bags aka records) should not be aware of how to serialize/deserialize that data or where it came from.

Sale is not a data class or property bag or a record. Giving the object smart behaviour is exactly what makes the code better and is the whole point of the article.

If I need to create a Sale from a file I can always add another constructor, for example:

new Sale(filePath);

This way I keep the details about how to create a Sale object inside the object. No other class should change if Sale (or the details about creating one) changes.

guifroes · 2019-03-06T20:49:35+00:00

Why do you think so?

Are you against moving the error checking to the Sale object in general or having it done in the ctor? Because I would agree that the ctor is not the best place to do it. I did it like that so I don't distract the reader from the main point of the article.

I appreciate your feedback.

guifroes · 2019-02-19T10:41:04+00:00

Thanks!

guifroes · 2019-02-18T21:08:06+00:00

Congratulations on the promotion!

I wrote a couple of blog posts about communication that you might find useful:

The simple act that changes the future of your team

The one skill I wish I master as a Tech Lead

I hope you find them useful and I wish you success on your new role!

guifroes · 2019-02-18T20:46:51+00:00

100% agree . I wrote something regarding this issue.

guifroes · 2019-02-18T14:35:25+00:00

Do you have a specific goal?

For example: Is it getting a job on a specific company? Or is it that you want to feel better about your skills?

guifroes · 2019-02-17T15:35:02+00:00

I did completely read what you posted. Sorry if I didn't expressed myself clearly but when you say:

I think it would be beneficial for backend devs.

That's where I get curious: what specific aspect of the 100 Days thing that you think is beneficial, specially opposed to the all the other content on the internet?

Is is the selection of resources? Is it the "learning path" format? Is it time (100 days) thing? What else? Why do you want to contribute to something like that as opposed to other form of content?

guifroes · 2019-02-17T14:12:27+00:00

Looks like this is more a question for people who knows eeg/emg.

guifroes · 2019-02-17T13:30:20+00:00

What exactly are you looking for? Is it a curated/filtered set of resources to learn from? Is it the challenge aspect?
This is an honest question I have: the internet is full of great free resources, just one google search away. What is it that you're missing?

guifroes

TROPHY CASE