/ˈhjuː.mə.nɔɪd/

10.7K posts

/ˈhjuː.mə.nɔɪd/ banner
/ˈhjuː.mə.nɔɪd/

/ˈhjuː.mə.nɔɪd/

@__ciox__

a high-powered mutant. cracked swe. compounding.

Magrathea Katılım Mayıs 2016
1K Takip Edilen1.2K Takipçiler
/ˈhjuː.mə.nɔɪd/
/ˈhjuː.mə.nɔɪd/@__ciox__·
@TheDumbTechGuy Someone told me to always confirm with the moon. In Nairobi, it’s 98.4% full You can confirm with your locality. And do with that information as you please 😂
English
1
1
4
416
/ˈhjuː.mə.nɔɪd/
/ˈhjuː.mə.nɔɪd/@__ciox__·
“Some may never live, but the crazy never die” Hunter S. Thompson
English
1
1
0
91
/ˈhjuː.mə.nɔɪd/ retweetledi
Naval
Naval@naval·
You aren’t starting a company. You’re laying bricks in the foundation of a skyscraper.
English
472
973
13.9K
674K
/ˈhjuː.mə.nɔɪd/
My opinion is there is no strict naming system in software. People just call themselves what they want, or what their role says. We even call ourselves engineers even though EBK may disagree with us In other fields like manufacturing, a senior engineer is someone with high-level autonomy, leadership, and system-level expertise, at least 5-8 years of continuous engineering and visible transition, PE and other relevant certifications in their fields and has a track record of managing complex projects.
English
0
0
7
507
Wamwea🇰🇪
Wamwea🇰🇪@wamweaaa·
What exactly makes one a "senior" software engineer? On LinkedIn a lot of people with less than 3 years experience put senior software engineer as their job title. Is there like a time or technical barrier that separates a normal engineer from a senior one?
English
4
5
49
5.9K
Wamwea🇰🇪
Wamwea🇰🇪@wamweaaa·
Retweet and interact with my pinned tweet for good luck 😅
English
1
0
1
222
/ˈhjuː.mə.nɔɪd/
@wamweaaa @notyroon Even if we had 100s of them, what’s the problem. The project is a lot useful in production than when not built. Just build and ship bro
English
0
0
5
170
Wamwea🇰🇪
Wamwea🇰🇪@wamweaaa·
@notyroon Show me another financial tracker made in Kenya nione. This isn’t an expense tracker
English
2
0
13
829
/ˈhjuː.mə.nɔɪd/
@WEGNERJOASH @_Briankorir Ndwize akitokea na belt majamaa wanahepea kwa window 😂 Only the main complex had that design though. Livi hadi Arthur haikua hivo Saai naona the new one ikona four floors, I don’t know their plan
English
0
0
0
25
Nashon
Nashon@WEGNERJOASH·
@_Briankorir Not sure if its a design requirement but our dormitories had windows that students could jump through. They were not higher than one floor. Which means even without the door open majority could escape.
English
1
0
9
1.6K
Brian
Brian@_Briankorir·
How comes the students struggled to open the dormitory door ? During our high school days the dormitory doors used to remain open. Locking of dormitory doors was prohibited.
English
55
517
3.7K
69.2K
/ˈhjuː.mə.nɔɪd/
That’s partly true. Both server and client have a lot of work in my view. There are maps, notifications, background services, and adaptive UI that are needed on mobile. Optimizing maps for battery, network and memory on android is not a simple task. There are backend engineers already working on apis and infrastructure. @nut3case is cooking something As they work on it, mobile can use BFF to keep the work going. The whole idea is to get started. And figure out things on the way.
English
0
0
1
40
Jr
Jr@RTJnr6·
@__ciox__ To be frank, I think most of the heavy lifting is on the backend, building the frontend isn't too difficult.
English
1
0
1
62
/ˈhjuː.mə.nɔɪd/
For a start, you are making a valid point about figuring out the market and all. For someone building a startup, that would be the case. But this is not a startup. It is an OSS. I would request you to go through that thread I quoted, and some of your concerns will be addressed. Second, most of us suffer from analysis paralysis. If you analyze the challenges of building a product that rivals any cab-hailing service, you will give up. The infrastructure, distribution, etc., will make the business not make sense. For an OSS, just get started and figure out the rest on the way. Most OSS products tackle markets dominated by big players. A lot of OSS die, the same way a lot of for-profit products die. In this case, the best case is to get started. I argued my technical choices with Sam because he asked technical questions. I shared project structure and architecture for the mobile client, and he wanted to understand why I made those choices.
English
0
0
1
14
Keronei lincoln
Keronei lincoln@lincoln_keros·
@__ciox__ @SamProgramiz Want to rival Uber and the first thing you do is create a project and argue about the technical choices? Figuring out the market and other things can easily make 90% of the work, I would recommend some field work first to establish why other competitors haven't oudone it.
English
1
0
0
28
Carlos Valentin
Carlos Valentin@CarlosBBuild·
Unpopular opinion I would only target iOS for mobile apps
English
40
0
64
8.9K
kalonzo
kalonzo@gnkalonzo·
@__ciox__ @jrobah Quite funny , we are now forced to live on two extreme ends.(almost binary). And we outliers are being pushed as the new normal. Hans , did a good one, explaining what numbers actually mean.
English
1
0
0
29
Waigoko Kimengemenge
I don't like how the internet is deliberately trying to make us angry for no reason at all. Angry about the new electric Ferrari design - 99% of us can't even afford one Angry about Lupita being cast in Odyssey movie - nobody has even watched the movie .... It's unhealthy
English
7
6
40
1.6K
Mugo L.
Mugo L.@mugokariuki_·
@__ciox__ @SamProgramiz Yeah that's fair. I thought sharing logic would help avoid duplicating the same work on both sides. But i get the direction you are going for, i'd be down to contribute to android.
English
2
0
1
60
/ˈhjuː.mə.nɔɪd/
My bias towards KMP is when you have really cracked Android engineers, like Square. Or when the budget is constrained, and you want a few Android engineers to do the whole mobile stack. Or coz iOS engineers are quite few, and more expensive than Android engineers. Or when you are doing a lot of logic on-device. None of that applies to what we are doing.
English
0
0
0
25
SamProgramiz
SamProgramiz@SamProgramiz·
@__ciox__ Perfect I will try to contribute but your approach requires a lot of knowledge on architecture and libraries I don’t use, maybe I will just help with QA and testing feedback
English
1
0
0
55